@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+acetone
+altonen
+dr|z3d
+eche|off
+hk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
AHOH
Arch
BubbRubb
Daddy_1
Dann
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest17402
Irc2PGuest5096
Irc2PGuest69353
Irc2PGuest89334
Leopold_
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SlippyJoe_
Stormycloud
T3s|4_
Teeed
amnesia_
ardu
b3t4f4c3___
cumlord
dr4wd3_
eyedeekay_bnc
idontpee
not_bob_afk
ohThuku1
onon_
phil
poriori_
profetikla
r00tobo
rapidash
rascal
solidx66
thetia
tr
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