From: James Blacklock <jamesblacklock@protonmail•com>
To: Luke Kenneth Casson Leighton <lkcl@lkcl•net>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 102, Issue 15
Date: Tue, 07 Nov 2023 21:56:22 +0000 [thread overview]
Message-ID: <4iOFtd5ttgeFZZ_kxQ3EJngEzXAFOXC2LAZfUaHe3vs5dVTTFkriWe-ksTEC4WPQO-Z7myE3bR7HGnPty5uE-QkKlzrnwE3FCM80IoL4HEs=@protonmail.com> (raw)
In-Reply-To: <CAPweEDw1VsFvQgBm=t=yQPgJQ-HEh5-9Po3JnBPt_qxF9JgPOQ@mail.gmail.com>
Agreed, email lists are the way. Personally I love reading the email list; it is a great resource to know what kinds of technical discussions are going on in the community. I certainly hope we can just migrate to a different email list.
On Tuesday, November 7th, 2023 at 3:20 PM, Luke Kenneth Casson Leighton via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>
> On Tuesday, November 7, 2023, <bitcoin-dev-request@lists•linuxfoundation.org> wrote:
>
> > Rooms can be E2E encrypted.
>
> please, NO.
>
> there are people who have such valuable skills that their
> lives are put in danger if they engage in encrypted conversations.
>
> additionally the entire point of an open project IS THAT IT IS OPEN.
>
> mailing lists are the lowest OPEN common denominator.
>
> l.
>
>
> --
> ---
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
next prev parent reply other threads:[~2023-11-07 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12287.1699383943.1202.bitcoin-dev@lists.linuxfoundation.org>
2023-11-07 20:20 ` Luke Kenneth Casson Leighton
2023-11-07 21:56 ` James Blacklock [this message]
2023-11-08 2:00 ` Luke Kenneth Casson Leighton
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='4iOFtd5ttgeFZZ_kxQ3EJngEzXAFOXC2LAZfUaHe3vs5dVTTFkriWe-ksTEC4WPQO-Z7myE3bR7HGnPty5uE-QkKlzrnwE3FCM80IoL4HEs=@protonmail.com' \
--to=jamesblacklock@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lkcl@lkcl$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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