IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/06/18
@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dolphinandcat
+dr|z3d
+hagen
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb1
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest32661
Irc2PGuest59134
Irc2PGuest79272
Irc2PGuest89963
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
T3s|4__
Teeed
ardu
b3t4f4c3__
bak83
boonst_
cumlord
dr4wd3_
duck
eyedeekay_bnc
onon_
poriori_
profetikla
r3med1tz
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
SilicaRice is there a "powered by i2p" logo one can use?
SilicaRice hmm... you can scan the DHT for destinations...
SilicaRice specifically, you can scan the DHT for destinations (or, in the case of encrypted leasesets, just the entries themselves) that use the same signing key
SilicaRice "Both of the client authorization mechanisms above provide privacy for client membership. An entity that only knows the Destination can see how many clients are subscribed at any time, but cannot track which clients are being added or revoked."
SilicaRice interesting...
SilicaRice is the 123 encrypted leaseset format implemented anywhere?
SilicaRice also, when using 123 encrypted leasesets, do you have to fetch what's effectively the *whole* list of clients just to get to the destination? because if so that's really inefficient
SilicaRice oh yeah you do
SilicaRice that's... unfortunate
SilicaRice makes it somewhat unusable for 10k+ entries