From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: A new collaborative editing package (maybe tangent) Date: Wed, 03 Jan 2024 22:59:11 -0500 Message-ID: References: <3E633CB5-B727-4933-8CF1-E1044CF39E70@gmail.com> <402A5724-BDDC-49A3-BE51-E122FB05D494@gmail.com> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24432"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Yuan Fu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 04 05:00:04 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rLEtn-0006Aa-Vh for ged-emacs-devel@m.gmane-mx.org; Thu, 04 Jan 2024 05:00:04 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rLEt9-00008c-1w; Wed, 03 Jan 2024 22:59:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rLEt7-00008C-Ht for emacs-devel@gnu.org; Wed, 03 Jan 2024 22:59:21 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rLEt7-0000qw-9B; Wed, 03 Jan 2024 22:59:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=gUqk6Z+p8/fcTDU6XCBkkzGTHI/DMTPj+jyt/D/AKBQ=; b=AO4MKD49LRbw nRoYp1hvfIE0UsiY3dXAWGislTtZNKiOS5HnMp3yZYxk8uoml9yhFnt640pJxqKjJylPINvKGydyO KvbtCPe7D0fZqbkewl4PyJO5PNgLEk1ELEvmxArYLuXnhm+j/ZFj89Vz2TYm6+CIDGefqZ8zuhV0g CCnbH49MuPRu+y3Mz6P+XJ+DMB76Oe0ILa/UVOZmsu1M52GYnQ6ZGlVB3eLWL9X6M00NDu/EY1cCr 16o/jt/lxwQ3ROxC8NV5R/DoJL3iOdT5P1vNzL9KyDzrRmBTXTKsfhOdZN1GD1Shh2xo8i9v6KxKH Ow7TyACOTKPEHwjaM3fHww==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1rLEsx-0003Z8-An; Wed, 03 Jan 2024 22:59:11 -0500 In-Reply-To: <402A5724-BDDC-49A3-BE51-E122FB05D494@gmail.com> (message from Yuan Fu on Sun, 31 Dec 2023 20:53:03 -0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314514 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > Since there are no shared documents, > > what do these collab servers communicate about? > Edits made by each user (essentially insertions and deletions). > > Why do they need to communicate at all? > So you can see what I inserted in the the shared document, and vice versa. That makes sense, but what puzzled mwthe your statement that it doesn't support "shared docs." Now it seems to support them. What was the intended meaning of that statement? It seemed to say that something was not supported -- what was that something? > The servers use webrtc for communication, which uses DTLS for > encryption. But as I said, collab-mode is not secure right now, > adding authentication and access control is on the TODO list. There's no hurry in getting everything finished. If these fit into the design, we can wait for them to be implemented. What we should do now, however, before installing anything, is decide what architecture we want to use for collaborative editing. For instance, is this the right protocol to use? Do we want to base communication on this protocol? Should we base access control on logging in to some other sort of service? Could we base it on access to a repo which is where the shared document is to be stored? We should decide those things now because changing them later may be difficult. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)