@eyedeekay
&eche|on
&zzz
+Irc2PGuest3601
+R4SAS
+RN
+StormyCloud
+acetone
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch2
Birdy
BubbRubb
Chrono
Daddy
Dann
DeltaOreo
Irc2PGuest12868
Irc2PGuest61394
Irc2PGuest65801
Irc2PGuest74254
Irc2PGuest79605
Irc2PGuest90985
Irc2PGuest92550
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycl1
T3s|4_
Teeed
aargh2
ac9f_
anontor2
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gellegery
makoto
matean
n1
nilbog
not_bob_afk
null911
poriori
profetikla
r00tobo_BNC
rapidash
solidx66
thetia
uop23ip
w8rabbit
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)