IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2024/11/18
@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+StormyCloud
+acetone
+cims
+dr|z3d
+eche|off
+hagen
+mareki2p
+mesh
+nilbog
+nyaa2pguy
+orignal
+postman
+psychopuck
+qend-irc2p
+snex
+utp
+wodencafe
+wssh
Arch
Dann
Holmes
Irc2PGuest14358
Irc2PGuest28384
Irc2PGuest51362
NiceBoat
OfficialCIA_
Onn4l7h
Onn4|7h
Over1
SilentWave
Sleepy
U1F642
Wikk_0_
Zapek
aargh4
ac9f
ahiru
ananas_
anontor
calamares
dr4wd3
duanin2
eyedeekay_bnc
leopold
mahlay
makoto
n2_
not_bob_afk2
poriori
profetikla
r00tobo
rapidash
test3847473
uop23ip
user1
vivid_reader56
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