IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/06/18
@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BravoOreo
BubbRubb
Chrono
Danny
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest5036
Irc2PGuest59861
Irc2PGuest63688
Onn4l7h
Onn4|7h
Over
Rogueone
Sisyphus
Sleepy
St1nt
T3s|4_
T3s|4__
Teeed
aargh
acetone_
aisle
ardu
b3t4f4c3___
cumlord
dr4wd3
duanin2
eyedeekay_bnc
nilbog
not_bob_afk
ohThuku1
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
uop23ip
w8rabbit
weko_
wew
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