IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/04/26
@eyedeekay
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+altonen
+dr|z3d
+hk
+lbt
+orignal
+postman
+radakayot
+snex
+weko
+wodencafe
Arch
BravoOreo
Dann
FreeB
FreefallHeavens_
Irc2PGuest11045
Irc2PGuest27999
Irc2PGuest28584
Irc2PGuest3338
Irc2PGuest59134
Irc2PGuest82579
Onn4l7h
Onn4|7h
Sleepy_
Soni
T3s|4_
Teeed_
aeiou_
aisle1
ardu
b3t4f4c3__
bak83
dickless
dr4wd3
enoxa
eyedeekay_bnc
hagen_
not_bob_afk
phil
plap
poriori_
profetikla
qend-irc2p
rapidash
solidx66_
u5657
uop23ip
w8rabbit
x74a6h
eche|off SilicaRice: ask here
SilicaRice hello, i2pgit.org is broken for github login? have you considered adding support for TLS-SRP on the SAM bridge? and does using the SAM bridge allow making HTTP connections as well as receiving HTTP connections on the same i2p addresses, simultaneously?
zzz eyedeekay, confusion over the news as predicted, see zzz.i2p
zzz SilicaRice, no plans for TLS-SRP
zzz SilicaRice, yes SAM supports connections in both directions simulataneously
SilicaRice does i2p support making use of low-reliability nodes (if requested by the application, e.g. simple HTTP clients and servers, not doing anything fancy with websockets), and does it support mobility (like switching from wifi to mobile, or between wifi networks)?
eche|on mostly yes,but depends on definitions
SilicaRice when it comes to low-reliability nodes, does it mean low-reliability nodes would still benefit the network? and for mobility, how fast can it switch over?
SilicaRice (this is about seamlessly embedding i2p, mostly)