IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/02/21
@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+RN_
+acetone
+dr|z3d
+hk
+lbt
+orignal
+postman
+weko
+wodencafe
An0nm0n
Arch
Dann
DeltaOreo
FreefallHeavens
GucciferZ
Irc2PGuest35128
Irc2PGuest43186
Irc2PGuest59134
Irc2PGuest61987
Irc2PGuest99418
Leopold
Nausicaa
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
SoniEx2
T3s|4_
T3s|4__
anon
b3t4f4c3__
bak83
boonst
carried6590
cumlord
dr4wd3
eyedeekay_bnc
l337s
not_bob_afk
poriori_
profetikla
qend-irc2p_
r3med1tz-
radakayot_
rapidash
scottpedia
segfault
shiver_
solidx66_
syncthing2
trust
u5657
uis
uop23ip
w8rabbit
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