@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+cims
+eche|off
+hagen
+mareki2p
+mesh
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+red
+snex
+utp
+wodencafe
Arch
Danny
Holmes
Irc2PGuest28384
Irc2PGuest84270
NiceBoat
OfficialCIA
Onn4l7h
Onn4|7h
Over1
Sleepy
T3s|4_
Wikk_0
Zapek
aargh4
ac9f
acetone_
ahiru
anontor2
calamares
dr4wd3
duanin2
eyedeekay_
eyedeekay_bnc
leopold
mahlay
makoto
n2
not_bob_afk
poriori
profetikla
r00tobo_BNC
rapidash
test7363673
thetia
uop23ip
val
vivid_reader56
x74a6
zelgomer
zzz
orignal, at the ratched layer we send the NSR back if the application doesn't respond
orignal
how long do you wait?
zzz
orignal, 1 second
orignal
thanks
orignal
so 1 sec
StormyCloud
I2P will be at Scale this year (https://www.socallinuxexpo.org/scale/23x) we have a few extra tickets if anyone wants to attend.
zzz
right. this is all at ratchet layer, doesn't matter if streamr or not, datagram or streaming. For anything that requires a response, as it says in the spec
orignal
beside this level is just a encyption and knows nothing about tunnels
zzz
yup
orignal
hence I have this issue in I2CP only
orignal
another question. when you receive NS message how do you find LS to send NSR to? by static key since you don't have destination yet
zzz
orignal, the LS is in the NS, we look though the cloves to find it, and the destination is in the LS
zzz
and the static key is in the first noise message (this is IK, not XK)