@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+acetone
+dr|z3d
+hk
+not_bob_afk
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BravoOreo
BubbRubb1
C341
Chrono
Daddy
Danny
Debian-GNU-Hurd-2025-released
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest29259
Irc2PGuest33339
Irc2PGuest34005
Irc2PGuest77721
Leopold_xmpp_
Onn4l7h
Over
Sisyphus_
Sleepy
StormyCloud
T3s|4_
Teeed
aargh
ardu
b3t4f4c3
bak83
cumlord
cumlord_
dr4wd3_
duanin2
eyedeekay_bnc
hagen_
kaffi
nilbog
nnm--
ohThuku1_
poriori
pory
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
u5657
uop23ip
w8rabbit
wew
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