@Xeha
@orignal
Arch
Danny
Irc2PGuest28384
Irc2PGuest75631
Irc2PGuest81267
Over
R4SAS
RN
ReturningNovice
StormyCloud
Strykar
U1F642
acetone
ahiru
ananas
duanin2
fidoid_
i2potus
ice_juice
itsAMe_
luvme
mareki2p
n2_
pinotto
poriori
qend-irc2p
r00tobo
r00tobo[2]
rapidash
sexy
uberius
x74a6
yeti
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