unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: A new collaborative editing package (maybe tangent)
Date: Wed, 03 Jan 2024 22:59:11 -0500	[thread overview]
Message-ID: <E1rLEsx-0003Z8-An@fencepost.gnu.org> (raw)
In-Reply-To: <402A5724-BDDC-49A3-BE51-E122FB05D494@gmail.com> (message from Yuan Fu on Sun, 31 Dec 2023 20:53:03 -0800)

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





  parent reply	other threads:[~2024-01-04  3:59 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 [this message]
2024-01-04  8:02           ` Dr. Arne Babenhauserheide
2024-01-05  0:33             ` Yuan Fu
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=E1rLEsx-0003Z8-An@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@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).