From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 102, Issue 15
Date: Tue, 7 Nov 2023 20:20:38 +0000 [thread overview]
Message-ID: <CAPweEDw1VsFvQgBm=t=yQPgJQ-HEh5-9Po3JnBPt_qxF9JgPOQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.12287.1699383943.1202.bitcoin-dev@lists.linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 678 bytes --]
next parent reply other threads:[~2023-11-07 20:47 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 [this message]
2023-11-07 21:56 ` [bitcoin-dev] bitcoin-dev Digest, Vol 102, Issue 15 James Blacklock
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='CAPweEDw1VsFvQgBm=t=yQPgJQ-HEh5-9Po3JnBPt_qxF9JgPOQ@mail.gmail.com' \
--to=lkcl@lkcl.net \
--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