@eyedeekay
&eche|on
&zzz
+Irc2PGuest3601
+R4SAS
+RN
+StormyCloud
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+qend-irc2p
+snex
Arch2
Birdy
BubbRubb
Chrono
Dann
DeltaOreo
Irc2PGuest27269
Irc2PGuest65801
Irc2PGuest65978
Irc2PGuest74254
Irc2PGuest79605
Irc2PGuest90985
Irc2PGuest92550
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
T3s|4_
Teeed
aargh2
ac9f_
anontor
b3t4f4c3__
cumlord
dr4wd3
duanin2
eyedeekay_bnc
gelleger1
leopold_
makoto
mareki2p_
matean
n1
nilbog
not_bob_afk
null912
poriori
profetikla
r00tobo_BNC
solidx66
thetia
uop23ip
w8rabbit
x74a6
xHarr
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