+R4SAS
+RN_
+T3s|4
+acetone
+mareki2p
+orignal
+postman
+qend-irc2p
AlaskaBear
Arch
Daddy_I2P
FreefallHeavens
Irc2PGuest23015
Irc2PGuest24082
Irc2PGuest30827
Irc2PGuest61348
Irc2PGuest6656
Irc2PGuest77286
MatrixBot
NiceBoat_
Onn4l7h
Onn4|7h
Over1
Romster_
Sisyphus
Sleepy
StormyCloud
T3s|4__
U1F642
Zapek
aargh3
ahiru_
ananas
anontor
b3t4f4c3___
cims
dr4wd3_
duanin2
eche|off
eyedeekay_
hagen_
leopold
mahlay
makoto
marek
marek22k
molybd2
n2_
nilbog
not_bob_afk
nyaa2pguy
o3d3
poriori
profetikla
quack_
r00tobo_BNC
rapidash
rednode
solidx66
stormycloud[m]
sublimia
test7363673
tr
u0_a292_2
uop23ip
wodencafe
zelgomer
zzz
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