public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Bryan Bishop <kanzure@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
Date: Tue, 7 Nov 2023 23:08:58 +0000	[thread overview]
Message-ID: <ZUrDip1Uf1/rRPIX@petertodd.org> (raw)
In-Reply-To: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>

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

On Tue, Nov 07, 2023 at 09:37:22AM -0600, Bryan Bishop via bitcoin-dev wrote:
> Anti spam has been an issue for the moderators. It's relentless. Without
> access to the underlying server, it has been difficult to fight spam. There
> is some support for filters in mailman2 but it's not great.

Since this is a technical mailing list it would be fine to require people to
pay a non-refundable anti-spam fee, eg via lightning, to gain the ability to
send messages. While this would require some custom software, it's probably
even possible to implement this if a third party is used for hosting, provided
they have some kind of API.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-11-07 23:09 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
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 [this message]
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=ZUrDip1Uf1/rRPIX@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=kanzure@gmail.com \
    /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