IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2024/11/18
@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+mareki2p
+orignal
+postman
+radakayot
+segfault
+snex
Arch2
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest53192
Irc2PGuest59134
Irc2PGuest59581
Irc2PGuest64993
Irc2PGuest69585
Irc2PGuest96449
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
aeiou
ardu
b3t4f4c3___
b4dab00m
bak83_
boonst
carried6590
cumlord
death
dr4wd3
duck
eyedeekay_bnc
not_bob_afk
onon_
phil1
phobos
pisslord
poriori_
profetikla
qend-irc2p
rapidash
shiver_1
solidx66
thetia
u5657
uop23ip
w8rabbit
x74a6
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