IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2025/09/08
~dr|z3d
@RN
@RN_
@Stormycloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%acetone
%ardu
%cumlord
+Onn4l7h
+Over
+Sh0ck
+Xeha
+hk
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+romer
+uop23ip
+waffles
+wew
Arch
BravoOreo
BubbRubb
C341
Danny
FreeRider
GnuHurd
Irc2PGuest10122
Irc2PGuest17149
Irc2PGuest74165
Irc2PGuest81794
Irc2PGuest83998
Irc2PGuest92336
Irc2PGuest96790
Leopold_xmpp
Liorar_
Meow
aisle1
anontor2
halloy13412
makoto
maylay
moe_
nilbog
nnm--
pisslord
pory
r00tobo[2]
shiver_
simprelay
solidx66
thetia
u5657
woodwose
zer0bitz
uop23ip has done reseed after 40min, dr|z3d netdb dat 600+, known 4k+
dr|z3d ok, uop23ip, thanks. very strange, but I'll have to investigate more.
dr|z3d 600 sounds a little on the high side tbh, the i2p process definitely has write permissions on that folder?
dr|z3d (you can check the timestamps for the dat files and ensure they're fairly recent, last 24 hours or so)
uop23ip yeah modified last 10min.
dr|z3d ok, thanks.
uop23ip thanks and good luck hunting! router runs fine besides this "issue" btw, so np
dr|z3d no worries, new build forthcoming shortly.
dr|z3d Blinded message
dr|z3d you may still see a reseed after 20m, uop23ip, still haven't identified why it's doing that, despite making code changes. hmm. it's not fatal, anyways. you can always specify i2p (http) tor as your socks proxy if you want to anonymize reseed requests while I get to the bottom of this.
dr|z3d another update landing soon...
dr|z3d Blinded message
dr|z3d ok, uop23ip, from where I'
dr|z3d *I'm sitting, looks like reseed is behaving now.
dr|z3d (famous last words)
dr|z3d zzz: zzzot warning, not sure it's noteworthy? > No listener found for protocol: 18 on port: 6969 from pool of 3 listeners
dr|z3d 18 is mux.