@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
AHOH
Arch
BubbRubb
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest37330
Irc2PGuest38625
Irc2PGuest82037
Irc2PGuest89334
Leopold_
Onn4l7h
Onn4|7h
Sisyphus_
Sleepy
T3s|4_
Teeed
ardu
b3t4f4c3__
bak83
cumlord
death
dr4wd3
duck
eyedeekay_bnc
mittwerk
not_bob_afk
poriori
profetikla
r00tobo_BNC
r3med1tz-
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
w8rabbit
weko_
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