IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/06/18
@eyedeekay
&eche|on
+R4SAS
+RN
+acetone
+dr|z3d
+hottuna
+orignal
+polistern
+postman
+weko
An0nm0n_
Arch
FreefallHeavens
Gid_
Irc2PGuest19856
Irc2PGuest2827392
Irc2PGuest77041
Leopold
Minogami
Onn4l7h
Onn4|7h
ProRu
Sleepy
Soni
Teeed
aargh3
anon1
b3t4f4c3__
eyedeekay_bnc
itsjustme_
limak
not_bob_afk
profetikla
qend-irc2p
rapidash
tbqdrn
theglitch
user
w8rabbit
x74a6
zer0bitz
zzz2
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