From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:58062) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibv44-0006KM-Mk for gwl-devel@gnu.org; Mon, 02 Dec 2019 18:25:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ibv43-0003CI-FJ for gwl-devel@gnu.org; Mon, 02 Dec 2019 18:25:12 -0500 Received: from sender4-of-o54.zoho.com ([136.143.188.54]:21469) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ibv42-00035K-WC for gwl-devel@gnu.org; Mon, 02 Dec 2019 18:25:11 -0500 References: From: Ricardo Wurmus Subject: Re: Reading over necrothread "Next steps for the GWL" -- switch from ssh to mosh? In-reply-to: Date: Tue, 03 Dec 2019 00:25:01 +0100 Message-ID: <87d0d69upe.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gwl-devel-bounces+kyle=kyleam.com@gnu.org Sender: "gwl-devel" To: Josh Marshall Cc: gwl-devel@gnu.org 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=E2=80=99t mind having this as an optional alternative transport, b= ut SSH is ubiquitous for better or worse, so I don=E2=80=99t think it should be replaced. ~~ Ricardo