&zzz
+FreefallHeavens
+Irc2PGuest61348
+R4SAS
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+mareki2p
+nilbog
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
Daddy_I2P
Irc2PGuest23015
Irc2PGuest24082
Irc2PGuest30827
Irc2PGuest6656
Irc2PGuest77286
MatrixBot
NiceBoat
Onn4l7h
Onn4|7h
Over1
Romster_
Sisyphus
Sleepy
Zapek
aargh3
ahiru_
ananas
anontor
b3t4f4c3___
cims
dr4wd3_
duanin2
eyedeekay_
hagen_
leopold
mahlay
makoto
marek
marek22k
molybd2
n2
not_bob_afk
nyaa2pguy
o3d3
poriori
profetikla
quack_
r00tobo_BNC
rapidash
rednode
solidx66
stormycloud[m]
sublimia
test7363673
u0_a292_2
uop23ip
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