IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/02/21
&zzz
+R4SAS
+RN
+Romster_
+Stormycloud
+acetone
+eche|off
+nilbog
+orignal
+postman
+sourceress
+wodencafe
Arch
Daddy_I2P
Danny
Gully
Irc2PGuest19485
Irc2PGuest31672
Irc2PGuest44504
Irc2PGuest47230
Irc2PGuest93219
NiceBoat
Onn4l7h
Over1
Sisyphus
SlippyJoe
T3s|4_
Teeed
Yotsu
Zapek2
__bob_
aargh3
ahiru_
ananas2
anontor
b3t4f4c3___
cims
duanin2
leopold
makoto
marek
marek22k
n2_
not_bob_afk2
o3d3_
poriori
profetikla
qend-irc2p_
r00tobo_BNC
rapidash
solidx66
sublimia
test3847473
uop23ip
urist_
user45
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