@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+hagen
+hk
+lbt
+orignal
+postman
+radakayot
+weko
+wodencafe
An0nm0n
Arch
Danny
DeltaOreo
Extractor
FreefallHeavens
Irc2PGuest17611
Irc2PGuest1833
Irc2PGuest30976
Irc2PGuest31002
Irc2PGuest58773
Irc2PGuest59134
Nausicaa
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
acetone_
aeiou
ardu
b3t4f4c3
boonst
cumlord
dickless
dr4wd3_
eyedeekay_bnc
not_bob_afk
onon_1
poriori
profetikla
qend-irc2p
r3med1tz-
rapidash
shiver_sc
solidx66_
thetia
u5657
uis
uop23ip
w8rabbit
x74a6
yoppie
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)