IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/02/04
@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest33667
Irc2PGuest51880
Irc2PGuest97218
Onn4l7h
RN_
Sisyphus
Sleepy_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m
bak83_
duanin2
eyedeekay_
john231
leopold
makoto
nilbog-
not_bob_afk
poriori_
profetik1
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
R4SAS zzz2: hi. I have question about problems with our irc server
R4SAS is this happens due to filters in irc client tunnel?
zzz R4SAS, what problems?
R4SAS zzz: clints can connect to channels, timed out or just disconnects because client didn't receive some protocol messages
zzz this is java clients connecting to ilita?
R4SAS but they will be published in next release
zzz yes, they need that fix
R4SAS so till next release they will keep flooding logs with disconnects? )))
zzz there may be other workarounds, like using a different IRC client, or maybe some configuration, I don't know
R4SAS like generic client tunnel?
zzz sure, that should work, but then you lose all the filter protection
R4SAS got it
zzz I posted about it on zzz.i2p/topics/3230 late December
R4SAS remember it :D
zzz R4SAS, of course, if you want to fix it now, you can disable v3 message tags on your server ))
R4SAS zzz: not sure if this possible