@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+cumlord
+dr|z3d
+eche|off
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Daddy_
Danny
FreefallHeavens
Irc2PGuest10338
Irc2PGuest19087
Irc2PGuest20240
Irc2PGuest21187
Irc2PGuest4438
Irc2PGuest57061
Irc2PGuest62398
Irc2PGuest81105
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Stormycloud_
Teeed
aargh2
ac9f_
acetone_
anontor
b3t4f4c3__
dr4wd3_
duanin2
duck
makoto
n1
noidea
not_bob_afk
nyaa2pguy
onon_
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
urist_
user1
vivid_reader56
w8rabbit
x74a6
zelgomer
zyx___
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