@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+cims
+hagen
+nilbog
+nyaa2pguy
+postman
+snex
Arch
Danny
Irc2PGuest17692
Irc2PGuest28384
Irc2PGuest78852
Irc2PGuest85111
Onn4l7h
Onn4|7h
Over1
SilentWave
Sleepy
T3s|4_
U1F642
Watson
Wikk_0
Zapek
aargh4
ac9f
acetone
ahiru
anontor
b3t4f4c3__
dr4wd3_
duanin2
eyedeekay_bnc
leopold
mahlay
makoto
marek
mareki2p_
n2
not_bob_afk2
orignal
poriori
profetik1
qend-irc2p_
r00tobo_BNC
rapidash
rednode
sahil
test7363673
uop23ip
urist_
vivid_reader56
wodencafe2
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)