+R4SAS
+RN_
+acetone
+orignal
+postman
+qend-irc2p
+sourceress
Birdy
Daddy_
Irc2PGuest30010
Irc2PGuest36077
Onn4l7h
Over
Sleepy
Teeed
Yotsu
__bob_
aargh3
ac9f
ananas2
b3t4f4c3__
duanin2
f00b4r
hababam
hagen_
leopold
makoto
marek
marek22k
noidea
not_bob_afk
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
uop23ip
urist_
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)