From: Yuan Fu <casouri@gmail.com>
To: rms@gnu.org
Cc: arne_bab@web.de, emacs-devel@gnu.org
Subject: Re: A new collaborative editing package (maybe tangent)
Date: Fri, 5 Jan 2024 23:17:25 -0800 [thread overview]
Message-ID: <3B16087C-7E99-494F-A826-2E67BE6E9918@gmail.com> (raw)
In-Reply-To: <E1rLyN5-0005RN-Lp@fencepost.gnu.org>
> On Jan 5, 2024, at 8:33 PM, Richard Stallman <rms@gnu.org> wrote:
>
> [[[ 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. ]]]
>
>> 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.
>
> This has the advantage of being similar to what we already use.
>
>> 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.
>
> ISTR that there was some doubt about whether OpenID could be used
> in the free world. That was discussed maybe 6 or more years ago.
> If it is useful, I can look up what was said back then and we could
> see whee it stands now.
>
Since OpenID is a protocol, what make it unsuitable for the free world?
> Would it be feasible to support both methods?
We’ll see. I haven’t thought too deeply into it.
Yuan
next prev parent reply other threads:[~2024-01-06 7:17 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
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 [this message]
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=3B16087C-7E99-494F-A826-2E67BE6E9918@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).