@eyedeekay
&zzz
+R4SAS
+RN_
+StormyCloud
+T3s|4
+cumlord
+dr|z3d
+hagen
+not_bob
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Daddy
Danny
DeltaOreo
FreefallHeavens
Guest99
Irc2PGuest1910
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest41816
Irc2PGuest59088
Irc2PGuest74254
Irc2PGuest78101
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
SlippyJoe
Stormycloud_
Teeed
aargh2
ac9f_
acetone_
anontor
b3t4f4c3___
dr4wd3
duanin2
duck
eyedeekay_bnc
leopold
makoto
mareki2p_
n1
onon_
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
wodencafe2
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