IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/02/21
&zzz
+R4SAS
+RN
+T3s|4
+dr|z3d
+eche|off
+hagen
+hk
+not_bob_afk
+postman
+snex
+weko
+wodencafe
Arch
BubbRubb1
C341
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest29044
Irc2PGuest37393
Irc2PGuest41581
Irc2PGuest52861
Irc2PGuest53893
Irc2PGuest82088
Onn4l7h
Onn4|7h
Over
RN_
Rogueone
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3__
cumlord
death
dr4wd3
duanin2
el_stupido
llamafan991
mareki2p_
nnm--
ohThuku1
orignal_
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
x74a6
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