@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+Romster
+T3s|4
+cims
+dr|z3d
+eche|off
+mareki2p
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
Danny
Irc2PGuest10884
Irc2PGuest47612
Irc2PGuest69494
Irc2PGuest71043
Irc2PGuest87513
MatrixBot
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
SlippyJoe
T3s|4_
Zapek
aargh4
acetone_
ahiru_
ananas_
anontor
b3t4f4c3___
calamares
duanin2
eyedeekay_
eyedeekay_bnc
ice_juice
leopold
lokzz
mahlay
makoto
marek
marek22k
n2_
not_bob_afk2
o3d3_
pepega
profetikla
quack
r00tobo
rapidash
rednode
stormycloud[m]
sublimia_
test7363673
uop23ip
x74a6
zelgomer
eyedeekay
Array Index Out of Bounds Exception
eyedeekay
And yeah we can catch it higher up
eyedeekay
hk we definitely should not try to recover and trim, the reason go-i2p thought that it can do that was because of an off-by-one we fixed a couple weeks ago
hk
understood, yeah that's what I assumed and it's what I implemented