From: Overthefalls <overthefalls@opengroupware•ch>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
Date: Mon, 13 Nov 2023 09:05:38 -0600 [thread overview]
Message-ID: <8abf319929b0a729eab5ad4659727ff250e10efd.camel@opengroupware.ch> (raw)
In-Reply-To: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
On Tue, 2023-11-07 at 09:37 -0600, Bryan Bishop via bitcoin-dev wrote:
Google Groups is another interesting option,
I don't think I'm the only person on this list that is strongly opposed
to using google for anything. They are too big and they have their hand
in everything, and their eyes (and analytics) on everything.
I remember when there were virtually no gmail email addresses that
posted to this list. Suddenly in 2020 or 2021, we had an influx of
gmail subscribers and posters. That didn't escape me then and it is not
lost on me now.
Email is great for public discussion for many reasons. The fact that
everyone gets a copy of the data, there is no single central authority
that can edit emails once they have been sent out. Anyone can archive
email messages, they can generally store or publish the data anywhere
they like. That is not the case with web forum content.
I like the lightning anti-spam fee idea. That would encourage me to
finally adopt lightning, and it would, I'm sure, produce some
interesting results for the list.
I don't think email should be out of the question. Does anyone besides
kanzure@gmail•com think that sticking with email is out of the
question?
Let's do what's necessary to stick with email.
[-- Attachment #2: Type: text/html, Size: 1699 bytes --]
next prev parent reply other threads:[~2023-11-13 15:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 15:37 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
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 [this message]
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=8abf319929b0a729eab5ad4659727ff250e10efd.camel@opengroupware.ch \
--to=overthefalls@opengroupware$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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