From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:43282) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibrwm-0006M2-Pc for gwl-devel@gnu.org; Mon, 02 Dec 2019 15:05:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ibrwl-0003mn-VJ for gwl-devel@gnu.org; Mon, 02 Dec 2019 15:05:28 -0500 Received: from mail-qk1-x733.google.com ([2607:f8b0:4864:20::733]:36273) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ibrwl-0003lk-RU for gwl-devel@gnu.org; Mon, 02 Dec 2019 15:05:27 -0500 Received: by mail-qk1-x733.google.com with SMTP id v19so910873qkv.3 for ; Mon, 02 Dec 2019 12:05:27 -0800 (PST) MIME-Version: 1.0 From: Josh Marshall Date: Mon, 2 Dec 2019 15:05:15 -0500 Message-ID: Subject: Reading over necrothread "Next steps for the GWL" -- switch from ssh to mosh? Content-Type: text/plain; charset="UTF-8" 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: gwl-devel@gnu.org 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.