@eyedeekay
&zzz
+R4SAS
+Stormycloud
+cumlord
+dr|z3d
+hagen
+mareki2p
+postman
+qend-irc2p
+snex
+user5
Alin
Arch
BubbRubb
Daddy
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest13210
Irc2PGuest14567
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest32330
Irc2PGuest51098
Irc2PGuest74254
Irc2PGuest84511
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
T3s|4_
T3s|4__
Teeed
aargh2
ac9f_
acetone_
anontor2
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gelleger2
leopold_
makoto
n1_
nilbog
orignal
poriori_
profetikla
r00tobo
rapidash
thetia
uop23ip
vivid_reader56
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