From: Ricardo Wurmus <rekado@elephly.net>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: Reading over necrothread "Next steps for the GWL" -- switch from ssh to mosh?
Date: Tue, 03 Dec 2019 00:25:01 +0100 [thread overview]
Message-ID: <87d0d69upe.fsf@elephly.net> (raw)
In-Reply-To: <CAFkJGRdq5Keh9BfWCXbiGQzAwWQqUe8Ma633m4NZaRsEsvbFEQ@mail.gmail.com>
Hi Josh,
> I'm catching up on the suggested readings. One thing I noticed which
> might allow more stable connections would be to switch from a ssh
> based communication method to a mosh based one. The main selling
> point is stability over changing and unstable connections.
I wouldn’t mind having this as an optional alternative transport, but
SSH is ubiquitous for better or worse, so I don’t think it should be
replaced.
~~ Ricardo
prev parent reply other threads:[~2019-12-02 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 20:05 Reading over necrothread "Next steps for the GWL" -- switch from ssh to mosh? Josh Marshall
2019-12-02 23:25 ` Ricardo Wurmus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0d69upe.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=joshua.r.marshall.1991@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).