IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/06/18
@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+hagen
+hk
+lbt
+orignal
+postman
+radakayot
+weko
+wodencafe
An0nm0n
Arch
Danny
DeltaOreo
Extractor
FreefallHeavens
Irc2PGuest17611
Irc2PGuest1833
Irc2PGuest30976
Irc2PGuest58773
Irc2PGuest59134
Irc2PGuest96937
Nausicaa
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
acetone_
aeiou
ardu
b3t4f4c3
boonst
cumlord
dickless
dr4wd3_
enoxa
eyedeekay_bnc
not_bob_afk
onon_1
poriori
profetikla
qend-irc2p
r3med1tz-
rapidash
shiver_sc
solidx66_
u5657
uop23ip
w8rabbit
x74a6
yoppie
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