IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/12/20
+R4SAS
+RN_
+T3s|4
+mareki2p
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
Daddy_I2P
Danny
FreefallHeavens
Irc2PGuest11549
Irc2PGuest18154
Irc2PGuest35412
Irc2PGuest44123
Irc2PGuest65303
Irc2PGuest77921
Irc2PGuest88140
MatrixBot
Onn4l7h
Onn4|7h
Over
Romster
Sisyphus
StormyCloud
T3s|4_
U1F642
Yotsu
Zapek
aargh3
acetone_
ahiru_
anontor
b3t4f4c3__
cims
dr|z3d
duanin2
eche|off
eyedeekay
hagen_
ice_juice
leopold
mahlay
marek
n2_
nilbog
noidea
not_bob_afk2
o3d3_
poriori
profetikla
quack_
r00tobo
rapidash
rednode
solidx66_
stormycloud[m]
sublimia
test7363673
uop23ip
urist_
vivid_reader56
x74a6
zelgomer
zzz
dr|z3d obscuratus: one to throw back at you. the tunnel.rejectHostile graph is one to keep an eye on.
obscuratus dr|z3d: Thanks, I'll have a look.
dr|z3d hostile requests are usually peers trying to put you in multiple hops in a single tunnel chain.
dr|z3d not sure if that's a bug somewhere or malicious intent.
zzz -10 with more ssu2 goodness
zzz obscuratus, FYI, I now understand why the peers were getting unbanned. dr|z3d is correct, it was fixed by the commit he referenced.
obscuratus zzz: OK, thanks
zzz zzz.i2p back after about an hour of maintenance gone wrong, apologies for the downtime