@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+dr|z3d
+hk
+mareki2p
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens_
HowardPlayzOfAdmin
Irc2PGuest21522
Irc2PGuest51104
Onn4l7h
Over
SigSegv
Sisyphus
Sleepy
St1nt
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3___
bak83_
cumlord
death
dr4wd3_
duanin2
duck
eyedeekay_bnc
hagen_
nilbog-
nnm--
not_bob_afk
ohThuku1
orignal
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
wodencafe
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