@Xeha
@orignal
Arch
BubbRubb1
Danny
Irc2PGuest44009
Irc2PGuest63096
Irc2PGuest74254
Irc2PGuest88931
Irc2PGuest93823
Meow
Onn4l7h
Over
RN
Romster
StormyCloud
Strykar
Yotsu
acetone
b3t4f4c3___
combed_tree328
duanin2
halloy13412
itsAMe
mareki2p_
n1
poriori_
qend-irc2p
r00tobo
rapidash
semantica
shiver_
u5657
x74a6
aisle
Was there any particular reasoning behind latency-aware tunnel selection falling back to standard tunnel selection when a tunnel within range fails to build? I'm still looking into optimizing I2P deployments of applications and services, and I'm wondering if there's a less obvious reason as to why this was chosen over stricter adherence to the latency configuration: github.com/PurpleI2P/i2pd/commit/e740d5f
aisle
282f302459b