@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest248832
Irc2PGuest47444
Irc2PGuest92548
Leopold_
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
Teeed
acetone_
ardu
b3t4f4c3__
bak83_
cumlord
death
dr4wd3
eyedeekay_bnc
not_bob_afk
onon_
poriori
profetikla
r00tobo
shiver_1
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
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)