&zzz
+FreefallHeavens
+R4SAS
+RN
+StormyCloud
+acetone
+cims
+dr|z3d
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+psychopuck
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
T3s|4
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
duanin2
i2potus
ice_juice
justaperson
luvme3
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
zzz
hmph was wondering why I had funny UTF8 in my logs and config files
zzz
fun fact, in Java 21 they changed the default time format
zzz
was Mar 21, 2026, 11:54:04 AM
zzz
now Mar 21, 2026, 11:54:04(UTF8 non-breaking thin space U+202F)AM
zzz
everything else is still regular spaces
zzz
cool
zzz
eyedeekay, gitssh down
eyedeekay
restarting it, should be back in 20m
dr|z3d
>> If you were running an earlier iteration of the + sessionbans -> iptables script, you'll want to update. significant bug fixes and optimizations in the latest iteration: github.com/I2PPlus/i2pplus/blob/master/docs/i2p-sessionban-nftables.md
dr|z3d
$ sudo ../i2p-scripts/i2p-sessionban-nftables.py --list-summary
dr|z3d
IPv4: 10055
dr|z3d
IPv6: 78
dr|z3d
With that in place, after around 6h uptime, router is at around 2.5K bans. Nice and manageable.
dr|z3d
oops, sorry, wrong channel.
zzz
eyedeekay, success was short-lived, gitssh down again
zzz
worked on 8th retry