@eyedeekay
&eche|on
&zzz
+Irc2PGuest50030
+R4SAS
+RN
+RN_
+StormyCloud
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Chrono2
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16211
Irc2PGuest18900
Irc2PGuest49440
Irc2PGuest64908
Irc2PGuest68990
Irc2PGuest82810
Irc2PGuest83248
Onn4l7h
Sleepy
SlippyJoe_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m_
bak83
dr4wd3_
duanin2
eyedeekay_bnc
idk_afk
makoto
mareki2p_
poriori_
profetikla
r00tobo
rapidash
shiver_1
solidx66_
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
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