@eyedeekay
&eche|on
&zzz
+Irc2PGuest70424
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+weko
Arch
Birdy
BubbRubb
Chrono
Daddy_
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest17506
Irc2PGuest51542
Irc2PGuest52250
Irc2PGuest55980
Irc2PGuest59003
Irc2PGuest62234
Irc2PGuest62240
Irc2PGuest70010
Onn4l7h
Sleepy
SlippyJoe
T3s|4_
aargh2
ac9f_
acetone_
b3t4f4c3___
bak83
dr4wd3
duanin2
eyedeekay_bnc
idk_afk
leopold
nilbog
not_bob_afk
poriori_
profetikla
r00tobo_BNC
r3med1tz-
rapidash
shiver_1
solidx66_
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
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