@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+orignal
+postman
+segfault
+snex
+weko
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest59134
Irc2PGuest59461
Irc2PGuest77557
Irc2PGuest85010
Leopold
Onn4l7h
Onn4|7h
Sisyphus_
Sleepy
T3s|4_
ardu
b3t4f4c3__
bak83
boonst
cumlord
dr4wd3_
duck
eyedeekay_bnc
meowking
not_bob_afk
phil
phobos_
pisslord
plap
poriori
profetikla
qend-irc2p
rapidash
shiver_
solidx66
u5657
uop23ip
w8rabbit
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