@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+dr|z3d
+hagen
+hk
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+weko
+wodencafe
AHON1
Arch
BubbRubb
C341
Daddy
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest46813
Irc2PGuest57893
Irc2PGuest61215
Irc2PGuest62061
Irc2PGuest82088
Leopold
Onn4l7h
Onn4|7h
SigSegv
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3__
bak83_
carried6590
cumlord
dr4wd3
eyedeekay_bnc
idontpee
ohThuku1
poriori
profetikla
r00tobo_BNC
rapidash
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