@eyedeekay
&zzz
+R4SAS
+RN_
+StormyCloud
+T3s|4
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Daddy_
Danny
DeltaOreo
FreefallHeavens
Guest99
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest32330
Irc2PGuest74254
Irc2PGuest76033
Irc2PGuest78101
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
T3s|4_
Teeed
Uncrushed
aargh2
ac9f_
acetone_
anontor
b3t4f4c3___
dr4wd3
duanin2
erniee
eyedeekay_bnc
leopold
makoto
n1
nilbog-
noidea
not_blob
not_bob_afk
onon_1
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
tr
u5657
uop23ip_
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)