@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+StormyCloud
+cims
+eche|off
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Danny
Irc2PGuest32271
Irc2PGuest32781
Irc2PGuest86084
MatrixBot
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
T3s|4
T3s|4__
Zapek
aargh4
ac9f
acetone_
ahiru_
ananas__
anontor
b3t4f4c3___
calamares
dr4wd3
dr|z3d
duanin2
eyedeekay_bnc
justaperson
leopold
lokzz_
mahlay
makoto
marek
n2_
not_bob_afk2
poriori
profetikla
quack
r00tobo_BNC
rapidash
rednode
stormycloud[m]
test7363673
uop23ip
vivid_reader56
x74a6
zelgomer
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