@Xeha
@orignal
Arch
Danny
Irc2PGuest30010
Irc2PGuest49364
Irc2PGuest51117
Irc2PGuest65656
Irc2PGuest67278
Onn4l7h
Over
R4SAS
RN_
Strykar
Yotsu
acetone_
ahiru
b3t4f4c3__
duanin2
hagen_
noidea
o3d3_
poriori
qend-irc2p
r00tobo
r00tobo[2]
rapidash
semantica
urist_
user_
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