@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+acetone
+dr|z3d
+hagen
+hk
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+segfault
+weko
+wodencafe
Arch
BubbRubb
Daddy
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest58427
Irc2PGuest70152
Irc2PGuest92548
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
SlippyJoe
T3s|4
T3s|4_
Teeed
ardu
b3t4f4c3___
b4dab00m
bak83
bak83_
boonst
cumlord
dr4wd3
eyedeekay_bnc
guest7621
not_human_
onon_1
phil
poriori
profetikla
r3med1tz
rapidash
shiver_
snex
solidx66
thetia
u5657
uop23ip
w8rabbit
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