@eyedeekay
&zzz
+FreefallHeavens
+Irc2PGuest86649
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+cims
+dr|z3d
+eche|off
+fa
+hagen
+mareki2p
+nilbog
+onon_
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Holmes
Irc2PGuest28384
Irc2PGuest33148
Irc2PGuest44044
Irc2PGuest48505
Irc2PGuest85693
Irc2PGuest95381
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
T3s|4_
[-_-]
aargh4
ahiru
ananas_
anontor2
dr4wd3_
duanin2
justaperson
mahlay
makoto
marek22k
n2
not_bob_afk
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
urist_
user1
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