@Xeha
@orignal
Arch
Danny
Irc2PGuest20240
Irc2PGuest57061
Irc2PGuest77260
Irc2PGuest78958
Meow
Onn4l7h
Over1
R4SAS
RN
RN_
Romster_
StormyCloud
Stormycloud_
Strykar
acetone
b3t4f4c3___
combed_tree328
duanin2
gellegery
hagen
itsAMe
mareki2p
n1_
ntty
onon_
poriori_
qend-irc2p
r00tobo[2]
r00tobo_BNC
rapidash
semantica
shiver_
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