@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+hagen
+hk
+lbt
+mareki2p
+orignal
+postman
+radakayot
+snex
+wodencafe
Arch
Danny
DeltaOreo
EnforcedParalegal
FreefallHeavens
Irc2PGuest12735
Irc2PGuest42284
Irc2PGuest56109
Irc2PGuest59134
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
T3s|4_
Teeed
Wired
acetone_
aeiou
ardu
b3t4f4c3__
bak83
cumlord
death
dr4wd3
eyedeekay_bnc
not_bob_afk
onon_
phil
poriori_
profetik1
qend-irc2p
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