@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+acetone
+dr|z3d
+hagen
+hk
+lbt
+postman
+weko
Arch
Danny
DeltaOreo
FreefallHeavens_
Irc2PGuest12249
Irc2PGuest25220
Irc2PGuest54664
Irc2PGuest59134
Irc2PGuest90091
Irc2PGuest90883
Irc2PGuest92478
Leopold_
Nausicaa
Onn4l7h
Onn4|7h
Sleepy
Soni
T3s|4_
Teeed
aeiou
aisle1
ardu
b3t4f4c3___
bak83_
boonst
defaultnick
dickless
dr4wd3_
enoxa
eyedeekay_bnc
foobar_
not_bob_afk
orignal_
phil
poriori
profetikla
qend-irc2p
radakayot_
rapidash
shiver_
solidx66
u5657
uop23ip
w8rabbit
wodencafe2
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