@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+altonen
+dr|z3d
+eche|off
+hagen
+orignal
+postman
+radakayot
+segfault
+snex
Arch2
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest30001
Irc2PGuest53192
Irc2PGuest59134
Irc2PGuest59581
Irc2PGuest96449
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
aeiou
ardu
b3t4f4c3___
bak83_
boonst
carried6590
cumlord
death
dr4wd3
duck
eyedeekay_bnc
ka2
mareki2p_
onon_1
phobos_
pisslord
poriori
profetikla
qend-irc2p
rapidash
shiver_1
solidx66
thetia
u5657
uop23ip_
w8rabbit
weko_
wodencafe2
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