From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
Date: Tue, 7 Nov 2023 18:48:58 +0100 [thread overview]
Message-ID: <3f90175e-b7f4-476c-a274-fcfe02bbb81f@schildbach.de> (raw)
In-Reply-To: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
On 07/11/2023 16.37, Bryan Bishop via bitcoin-dev wrote:
> We would like to request community feedback and proposals on the future
> of the mailing list.
>
> [...]
Have you considered switching to Matrix? It's federated, much like
e-mail. It's censorship resistant, in the sense that any participating
homeserver keeps a copy of a room. And everyone can run their own
homeserver in the Matrix network.
Rooms can be E2E encrypted. For an email list replacement this is
probably not relevant, however any person-2-person communication would
benefit from being encrypted.
Synapse is the currently best developed home server that implements the
Matrix specification. It's much easier to run than an email server +
mailing list combo.
Much like E-Mail and IRC, there is a huge ecosystem of Matrix clients to
choose from.
I'm aware the UI of most Matrix clients is more suitable for a chat
system than lengthy email discussions. However, thanks to "threads",
there is no reason it could be used like that.
https://matrix.org/
https://github.com/matrix-org/synapse
next prev parent reply other threads:[~2023-11-07 17:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 15:37 [bitcoin-dev] Future of the bitcoin-dev mailing list Bryan Bishop
2023-11-07 16:12 ` Andrew Chow
2023-11-08 9:05 ` email
2023-11-07 17:03 ` Ademan
2023-11-07 18:14 ` Andrew Chow
2023-11-07 19:41 ` Christopher Allen
2023-11-07 22:24 ` Ryan Breen
2023-11-07 22:59 ` Peter Todd
2023-11-07 20:15 ` Ademan
2023-11-09 4:03 ` William Casarin
2023-11-07 23:07 ` Peter Todd
2023-11-07 17:48 ` Andreas Schildbach [this message]
2023-11-07 20:07 ` David A. Harding
2023-11-07 21:03 ` Keagan McClelland
2023-11-07 20:57 ` Tao Effect
2023-11-07 22:10 ` ponymontana
2023-11-07 23:08 ` Peter Todd
2023-11-08 14:29 ` Emil Pfeffer
2023-11-08 3:56 ` Anthony Towns
2023-11-13 2:58 ` Antoine Riard
2023-11-13 15:05 ` Overthefalls
2023-11-13 18:51 ` alicexbt
2023-11-14 15:32 ` Overthefalls
2023-11-11 10:54 vjudeu
2024-01-04 13:50 ` Brad Morrison
[not found] <mailman.15.1699963203.5599.bitcoin-dev@lists.linuxfoundation.org>
2023-11-14 12:32 ` Ali Sherief
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f90175e-b7f4-476c-a274-fcfe02bbb81f@schildbach.de \
--to=andreas@schildbach.de \
--cc=bitcoin-dev@lists.linuxfoundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox