@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+acetone
+dr|z3d
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
AHOH
Arch
BubbRubb1
C341
Daddy
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest12542
Irc2PGuest43371
Irc2PGuest46813
Irc2PGuest57893
Irc2PGuest61215
Irc2PGuest82088
Leopold
Onn4l7h
Onn4|7h
SigSegv
Sleepy
SlippyJoe_
Stormycloud
T3s|4_
Teeed
aargh
ardu
b3t4f4c3__
b4dab00m_
bak83_
carried6590
cumlord
dr4wd3
eyedeekay_bnc
idontpee
ohThuku1
poriori
profetikla
r00tobo_BNC
rapidash
solidx66
thetia
u5657
uop23ip
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