@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest33667
Irc2PGuest51880
Irc2PGuest97218
Onn4l7h
RN_
Sisyphus
Sleepy_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m
bak83_
duanin2
eyedeekay_
john231
leopold
makoto
nilbog-
not_bob_afk
poriori_
profetik1
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
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