+R4SAS
+RN
+Romster
+cumlord
+dr|z3d
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Birdy
BubbRubb1
Chrono
Daddy
Danny
DeltaOreo
Guest99
Irc2PGuest12767
Irc2PGuest28078
Irc2PGuest47819
Irc2PGuest63096
Irc2PGuest6790
Irc2PGuest718
Irc2PGuest74254
Irc2PGuest76277
Irc2PGuest88931
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Teeed
aargh2
ac9f
acetone_
anontor
b3t4f4c3___
dr4wd3
duanin2
eyedeekay_bnc
gelleger1
makoto
mareki2p_
matean
n1_
namenick
nilbog
poriori_
profetikla
r00tobo
rapidash
shiver_1
solidx66_
thetia
uop23ip
vivid_reader56
w8rabbit
x74a6
zzz
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