@eyedeekay
&zzz
+R4SAS
+RN
+T3s|4
+acetone
+altonen
+dr|z3d
+hagen
+hk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
+y2kboy23
Arch
BubbRubb1
Daddy
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest31631
Irc2PGuest41581
Irc2PGuest92548
Irc2PGuest95056
Leopold
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SlippyJoe_
StormyCloud_
T3s|4_
T3s|4__
Teeed
ardu
b3t4f4c3___
bak83_
boonst
defaultnick
dr4wd3_
eyedeekay_bnc
guest7621
not_bob_afk
not_human_
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
tr
u5657
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)