@Xeha
@orignal
Arch
Danny
FatherTime
Irc2PGuest28384
Irc2PGuest32652
Irc2PGuest37450
OfficialCIA
Over
R4SAS
RN_
Romster
StormyCloud
Strykar
U1F642
acetone_
ahiru
duanin2
fidoid
hagen
ice_juice
itsAMe
mareki2p
n2_
poriori
qend-irc2p
r00tobo
r00tobo[2]
rapidash
user_
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