@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+StormyCloud
+acetone
+cims
+eche|off
+hagen
+mareki2p
+mesh
+nilbog
+nyaa2pguy
+orignal
+postman
+psychopuck
+sidereal
+snex
+utp
+wodencafe
Arch
Dann
Holmes
Irc2PGuest17117
Irc2PGuest28384
Irc2PGuest89379
NiceBoat
OfficialCIA
Onn4l7h
Onn4|7h
Over
SilentWave
Sisyphus
Sleepy
T3s|4_
Wikk__
Zapek
aargh4
ac9f
ahiru
ananas
calamares
dr4wd3
duanin2
eyedeekay_bnc
fa
ice_juice
ka2
mahlay
makoto
n2_
not_bob_afk
profetikla
qend-irc2p_
r00tobo_BNC
rapidash
test3847473
thetia
uop23ip
user1
vivid_reader56
x74a6
zelgomer
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