@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+acetone
+dr|z3d
+hottuna
+postman
+weko
An0nm0n
Arch
FreefallHeavens
Hidenet1
Irc2PGuest19856
Irc2PGuest2827392
Irc2PGuest33877
Irc2PGuest62859
Irc2PGuest68850
Irc2PGuest95543
Leopold
Onn4l7h
Onn4|7h
Palimpsest
ProRu
Sleepy
Soni
T3s|4_
Teeed
aargh3
admin
anon
b3t4f4c3__
cheddah
eyedeekay_bnc
itsjustme_
limak
not_bob_afk
orignal_
profetikla
qend-irc2p
rapidash
tbqdrn
theglitch
w8rabbit
x74a6
yourtrueself
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)