unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: A new collaborative editing package (maybe tangent)
Date: Thu, 4 Jan 2024 16:33:55 -0800	[thread overview]
Message-ID: <D9B0FF5F-B018-4369-B69A-C74856762F4E@gmail.com> (raw)
In-Reply-To: <87wmspwmiw.fsf@web.de>



> On Jan 4, 2024, at 12:02 AM, Dr. Arne Babenhauserheide <arne_bab@web.de> wrote:
> 
> 
> Richard Stallman <rms@gnu.org> writes:
>> What we should do now, however, before installing anything,
>> is decide what architecture we want to use for collaborative editing.

I don’t think we are installing anything into Emacs. Collab-mode, if ever completes, will be like any other Emacs package.

>> 
>> For instance, is this the right protocol to use?
>> Do we want to base communication on this protocol?
> 
> The decision for OT seems to already be taken and may not be easy to
> change midflight, so I don’t know whether discussing this part has much
> merit.

Also, since what ever protocol collab-mode uses will be limited to collab-mode itself, I don’t think the protocol is very interesting to discuss anyway.

> 
>> 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?
> 
> And which methods are already well-supported in Rust?

I’ve thought about using public keys for authentication. Users would share their public keys through secure side-channel, then it’s easy to verify you are connecting to the person you think you are connecting to.

I also thought about adding OpenID support to the signaling server, such that the signaling server can endorse each user’s identify. Is is obviously more complicated, and requires the user to trust the signaling server.

Yuan


  reply	other threads:[~2024-01-05  0:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30  4:22 A new collaborative editing package (maybe tangent) Yuan Fu
2023-12-30  5:28 ` Karl Fogel
2023-12-30 10:56   ` Philip Kaludercic
2024-01-02  3:16     ` Richard Stallman
2023-12-30 19:49   ` Yuan Fu
2023-12-31 15:33     ` T.V Raman
2024-01-01  4:35       ` Yuan Fu
2024-01-01 15:49   ` Richard Stallman
2024-01-02  3:54     ` Yuan Fu
2024-01-05  4:22       ` Richard Stallman
2023-12-30  8:56 ` Aw: " Arne Babenhauserheide
2023-12-30 20:09   ` Yuan Fu
2024-01-01  3:32     ` Richard Stallman
2024-01-01  4:53       ` Yuan Fu
2024-01-01 23:09         ` Stefan Kangas
2024-01-02  3:45           ` Yuan Fu
2024-01-04  3:59         ` Richard Stallman
2024-01-04  8:02           ` Dr. Arne Babenhauserheide
2024-01-05  0:33             ` Yuan Fu [this message]
2024-01-06  4:33               ` Richard Stallman
2024-01-06  7:14                 ` Yuan Fu
2024-01-08  3:48                   ` Richard Stallman
2024-01-09  2:49                     ` Richard Stallman
2024-01-06  4:33               ` Richard Stallman
2024-01-06  7:17                 ` Yuan Fu
2024-01-08  3:48                   ` Richard Stallman
2024-01-07  4:28             ` Richard Stallman
2024-01-07  4:28             ` Richard Stallman
2024-01-07  7:06               ` Yuan Fu

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D9B0FF5F-B018-4369-B69A-C74856762F4E@gmail.com \
    --to=casouri@gmail.com \
    --cc=arne_bab@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).