public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl•net>
To: James Blacklock <jamesblacklock@protonmail•com>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
	<bitcoin-dev@lists•linuxfoundation.org>,
	Alain Williams <addw@phcomp•co.uk>
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 102, Issue 15
Date: Wed, 8 Nov 2023 02:00:00 +0000	[thread overview]
Message-ID: <CAPweEDx7_a6rfat=DeXn3FeYwRZWp8GTu4N9rvRywQuxfNTJMg@mail.gmail.com> (raw)
In-Reply-To: <4iOFtd5ttgeFZZ_kxQ3EJngEzXAFOXC2LAZfUaHe3vs5dVTTFkriWe-ksTEC4WPQO-Z7myE3bR7HGnPty5uE-QkKlzrnwE3FCM80IoL4HEs=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]

On Tuesday, November 7, 2023, James Blacklock <jamesblacklock@protonmail•com>
wrote:

> 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.

i have a friend alain williams who runs lists.phcomp.co.uk
and is competent at it. was the UKUUG Chair err 25 years ago?
cc'd.

the other lowest-common-denominator method is of course nntp
newsgroups (eternal-september.org run an excellent spam-free
one) and i do not mean "newsgroups via groups.google.com",
i mean *actual* nntp newsgroups, you know, the ones that have
been running for 40 years and everyone has forgotten even
exist? :)

they were and always have been distributed and distributable
(and spam-free *if* run properly) and i am sure the owner of
eternal-september would be happy to host/distribute bitcoin-dev.

another idea is public-inbox which actually stores
an entire mail archive *in a git repository*
https://github.com/nojb/public-inbox

  public-inbox implements the sharing of an email inbox
  via git to complement or replace traditional mailing lists.
  Readers may read via NNTP, IMAP, Atom feeds or HTML archives.

public-inbox can be "initialised" from a mailman archive
so you can have the entire past history of messages in
the git repo as well.  it's really quite sophisticated.

if anyone doesn't like "email bcuz old", or wants to remain
anonymous, they can always get a protonmail account, use
mail-forwarders, and TOR. and if they are happy to use nntp they can
register
on eternal-september.org, which then allows them to send and
receive... and then use TOR-proxy.

all doable *without* having to install something that will
consume alarmingly high resources and cost a fortune in hosting
every month.

l.

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

-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

[-- Attachment #2: Type: text/html, Size: 3582 bytes --]

      reply	other threads:[~2023-11-08  2:00 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
2023-11-08  2:00     ` Luke Kenneth Casson Leighton [this message]

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='CAPweEDx7_a6rfat=DeXn3FeYwRZWp8GTu4N9rvRywQuxfNTJMg@mail.gmail.com' \
    --to=lkcl@lkcl$(echo .)net \
    --cc=addw@phcomp$(echo .)co.uk \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=jamesblacklock@protonmail$(echo .)com \
    /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