IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2026/05/27
@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+cims
+dr|z3d_
+eche|off
+fa
+hagen
+nilbog
+onon_
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Birdy
Holmes
Irc2PGuest20837
Irc2PGuest28384
Irc2PGuest44044
Irc2PGuest48505
Irc2PGuest53214
Irc2PGuest95381
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
T3s|4_
aargh4
acetone_
ahiru
ananas
anontor
dr4wd3
dr|z3d
duanin2
justaperson
leopold
makoto
marek22k
mareki2p_
maylay
n2_
not_bob_afk2
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
user1
w8rabbit
x74a6
zelgomer
fa Even if the end-user does not change encryption settings and keeps the defaults, the router update will not update their encryption type settings to the current default of 6,4. I think this happens because during I2P router first run the default encryption option is written to the router config file and is indistinguishable from user specific choice.
jpk68 zzz: No, all of them seem to