+R4SAS
+RN_
+T3s|4
+acetone
+mareki2p
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+wodencafe
Irc2PGuest16019
Irc2PGuest35412
NiceBoat
Onn4l7h
Over
Sisyphus
T3s|4_
Teeed
aargh4
ahiru
ananas
b3t4f4c3___
dr|z3d
duanin2
marek
n2_
not_bob_afk2
o3d3
poriori
profetikla
r00tobo
sahil
solidx66
uop23ip
urist_
x74a6
zelgomer
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)