&zzz
+R4SAS
+RN_
+T3s|4
+eche|off
+nilbog
+orignal
+postman
+qend-irc2p
+sourceress
Arch
Birdy
Danny
Irc2PGuest30010
Irc2PGuest36077
Irc2PGuest49364
Irc2PGuest51117
Irc2PGuest6564
Irc2PGuest65656
Irc2PGuest67278
Irc2PGuest74235
Irc2PGuest83482
Irc2PGuest99117
MatrixBot
Onn4l7h
Over
Sleepy
Teeed
Yotsu
__bob_
aargh3
ac9f
acetone_
ahiru
anontor
b3t4f4c3__
cims
dr4wd3_
dr|z3d
duanin2
hababam
hagen_
leopold
makoto
marek
marek22k
noidea
not_bob_afk2
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
stormycloud[m]
test7363673
uop23ip
urist_
user_
zelgomer
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
R4SAS
I remember that you've did changes here: i2pgit.org/idk/i2p.i2p/-/commit/faa1bf117a60a6c42be49b96f8310443d2ee1a00
zzz
this is java clients connecting to ilita?
R4SAS
but they will be published in next release
R4SAS
yes
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