IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2024/11/18
@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+RN_
+StormyCloud
+acetone
+cims
+eche|off
+fa
+hagen
+nilbog
+onon_
+orignal
+postman
+red
+snex
+wodencafe
Arch
Holmes
Irc2PGuest28384
Irc2PGuest38263
Irc2PGuest44044
Irc2PGuest61007
Irc2PGuest95381
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
T3s|4_
Zapek2
[-_-]
aargh4
ahiru
anontor2
calamares
distractedlawyer
dr4wd3_
dr|z3d
duanin2
ice_juice
justaper1
leopold_
makoto
marek22k
maylay
n2_
not_bob_afk2
pinotto
poriori
profetikla
qend-irc2p_
r00tobo
rapidash
test7363673
uop23ip
urist_
user1
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