@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+acetone
+altonen
+dr|z3d
+eche|off
+hk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
AHOH
Arch
BubbRubb
Daddy_1
Dann
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest17402
Irc2PGuest5096
Irc2PGuest69353
Irc2PGuest89334
Leopold_
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SlippyJoe_
Stormycloud
T3s|4_
Teeed
amnesia_
ardu
b3t4f4c3___
cumlord
dr4wd3_
eyedeekay_bnc
idontpee
not_bob_afk
ohThuku1
onon_
phil
poriori_
profetikla
r00tobo
rapidash
rascal
solidx66
thetia
tr
uop23ip
w8rabbit
wew
x74a6
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)