IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/02/21
@eyedeekay
&zzz
+FreefallHeavens
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+cims
+dr|z3d
+eche|off
+fa
+nilbog
+orignal
+postman
+psychopuck
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Dann
Holmes
Irc2PGuest2724
Irc2PGuest28384
Irc2PGuest37550
Irc2PGuest52621
Irc2PGuest67643
Irc2PGuest74608
Irc2PGuest89138
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
T3s|4_
Zapek
aargh4
ahiru
anontor
calamares_
dr4wd3_
duanin2
ice_juice
justaperson
leopold
makoto
maylay
n2
not_bob_afk
pinotto
poriori
profetikla
rapidash
rotten_egg
sahil
test3847473
uop23ip
user1
vivid_reader56
w8rabbit
x74a6
zelgomer
dr|z3d zzz: re stormycloud, what about implementing a whitelist for router families to exclude them from sybil analysis?
dr|z3d assuming stormycloud's happy to put all his routers in the same family, a whitelist would fix the issue re sybils bans.
zzz that's one solution, yes
dr|z3d could a whitelist be made to function the same way as the blacklist does over the news feed? if so, then you've got a dynamic solution that wouldn't require router updates, once implemented.
zzz perhaps
dr|z3d whitelist could potentially allow for families, ip addresses, router hashes, not that different from the way the blacklist functions, with something in the console to view/manage existing entries.
zzz release tagged and pushed