@eyedeekay
&eche|on
&zzz
+FreefallHeavens
+R4SAS
+RN
+Romster
+acetone
+cims
+hagen
+nilbog
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Dann
Holmes
Irc2PGuest12976
Irc2PGuest1526
Irc2PGuest28234
Irc2PGuest3143
Irc2PGuest32287
Irc2PGuest51098
Irc2PGuest57041
NiceBoat
OfficialCIA_
Onn4l7h
Onn4|7h
Over
SilentWave
Sisyphus
Sleepy
Wikk__
Zapek
aargh4
ac9f
ahiru
ananas_
calamares_
dr4wd3
dr|z3d
duanin2
fa
hamstring1540
leopold_
mahlay
makoto
n2_
not_bob_afk2
poriori
pory
profetikla
r00tobo_BNC
rapidash
test3847473
thetia
unit86
uop23ip
user1
vivid_reader56
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)