&zzz
+R4SAS
+RN_
+StormyCloud
+eche|off
+mareki2p
+mesh
+nilbog
+orignal
+postman
+qend-irc2p
+wodencafe
Arch
Daddy_I2P
Danny
FreefallHeavens
Irc2PGuest12184
Irc2PGuest39024
Irc2PGuest95549
Irc2PGuest96214
NiceBoat
Onn4l7h
Onn4|7h
Over1
Romster_
Sisyphus_
Sleepy
Zapek
__bob_
aargh3
acetone_
ahiru_
anontor
b3t4f4c3___
dfhj
dr4wd3
duanin2
eyedeekay_
f00b4r
hagen_
leopold
makoto
marek
marek22k
n2_
not_bob_afk
nyaa2pguy
o3d3
poriori
profetikla
r00tobo_BNC
rapidash
rednode
solidx66
sublimia
test3847473
uop23ip
urist_
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