@Xeha
@orignal
Arch
BubbRubb
Danny
Irc2PGuest51880
Irc2PGuest95213
Irc2PGuest97218
Irc2PGuest99581
Meow
R4SAS
RN
RN_
StormyCloud
acetone
b3t4f4c3__
b4dab00m
combed_tree328
duanin2
halloy13412
john231
ntty
poriori_
r00tobo[2]
r00tobo_BNC
rapidash
semantica
shiver_
sidereal
thetia
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