path: root/09/ca644ccf31e7849b9c39b4e3bf58972d6c5139

Return-Path: <ademan555@gmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 43972C0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 17:03:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 11F3F6079E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 17:03:47 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 11F3F6079E
Authentication-Results: smtp3.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20230601 header.b=ShBte/3o
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 94g6zv5Jbr0g
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 17:03:44 +0000 (UTC)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com
 [IPv6:2a00:1450:4864:20::22f])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 4200C61420
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 17:03:44 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 4200C61420
Received: by mail-lj1-x22f.google.com with SMTP id
 38308e7fff4ca-2c509f2c46cso81928871fa.1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 07 Nov 2023 09:03:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1699376622; x=1699981422;
 darn=lists.linuxfoundation.org; 
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=VwT5ZeMHu2Xio27t9vL85+UUTdx3Z5djzmhy29RYhmA=;
 b=ShBte/3oaNVqCgboDdjNtwFpXb3cB1crZnaqA8a+d1csqruEmbiuJSq4tYo/mFqQAJ
 7nDOftd6BYhzudgRj4e4siGsvbbT4+SDEE5VyZc9LKFJL64fwXWOUvOoFiDq3gzBwQnf
 tCmqrridKXX0o4HF9owM7/kp54Aq6MrUxgKWZU7AIsDiOv63HCiYD07Jz+vVskbRqb3X
 6nYAO7S2/NMHqTYtSWYYC5EBgDe/KT9wfjtqQ9oYjA6Njc8U+pziByi9cY84au0E8Nir
 CgtCFNb+YeUTQrf2SaakI7I8mL1QeqVZ0Dy0lf1IUt/PfRlDkp1DTYWerHbElZZu5lrC
 W6MA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1699376622; x=1699981422;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=VwT5ZeMHu2Xio27t9vL85+UUTdx3Z5djzmhy29RYhmA=;
 b=ozSor857QXOtEaQgAFaRl07nRXPWl54ZcXdFRb3GhpiJVDprrowwDI7Ki7QwqrGREu
 qu8Y/PdDiamBpX5e5V721LNx0pVvNUhHMM0rDLvV3JeQXI3w97RJMJMNAXDvfKJdXclL
 l6yyikaNzqT+boTe8J7sv1UmI8o5vw0xFCtcWY94J1B8p6yAfWPXStSVfGD0Tb9dgnMb
 9AlY6Ybw7JkB32WnDuCfdmYKdDGqNnJCfh9Ie0FVki0AJXMqK2l0fzQ9wKmrN0UjP60P
 8SDJlO5R9qiNAqB7x4GRIKdYMOhDlVvJbTfs4PWP98mjlnG/n/9YygPuoaTViY+lTCVP
 yh+w==
X-Gm-Message-State: AOJu0YzaLKrurGZwrZNMR3spSHj1HEJ5Z/JB7DaW071+aSFK3EsdVdvY
 7EPeh3oJs8LrIksLI9osM1cD5XISt3d6qD1QdWE=
X-Google-Smtp-Source: AGHT+IHTh3X8SZ8NaGGmMc3+U/9Igtg6e/+tsyGBg+fZyWAvC0+iRTrD9GtFF0+hFBHh2zVDfPHIfF1WjC+Kss/ZPFw=
X-Received: by 2002:a2e:8043:0:b0:2c5:70f:614a with SMTP id
 p3-20020a2e8043000000b002c5070f614amr25515429ljg.17.1699376621716; Tue, 07
 Nov 2023 09:03:41 -0800 (PST)
MIME-Version: 1.0
References: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
In-Reply-To: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
From: Ademan <ademan555@gmail.com>
Date: Tue, 7 Nov 2023 11:03:30 -0600
Message-ID: <CAKwYL5ERT0zH=kcpPwqWe2Q2Gtn+Lj5nQF14yzAZ2nhn8AdD6A@mail.gmail.com>
To: Bryan Bishop <kanzure@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000e08a66060992f3da"
X-Mailman-Approved-At: Tue, 07 Nov 2023 17:20:08 +0000
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2023 17:03:47 -0000

--000000000000e08a66060992f3da
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Bryan,

I don't really want my first (and last?) devlist message to be a fairly
off-the-cuff post on this topic, but here we go anyway.

At the risk of sounding like a nostr evangelist (I promise I'm not), I want
to suggest nostr as a potential replacement to the mailing list. A decent
chunk of software would need to be written, but none of the alternatives
seem particularly attractive to me. I particularly dislike the idea of
locking into a single siloed forum service like the bitcointalk forums. I
realize I may be in the minority of course.


Nostr enables the ML team to outsource all of its biggest burdens, if it
chooses:

- mail server blocking is N/A to nostr

- Hosting costs are completely outsourced unless the ML team chooses to
host a relay.

- Archives and web portal access can be similarly outsourced because any
nostr archive is self-authenticating.

- The ML team can also choose to completely outsource moderation, as nostr
is (more or less) permissionless by nature.
  I understand if there is a "blessed" communication system, the ML team
would probably prefer to keep it high quality. To that end there are
proposals for proof-of-work, and web of trust based blocklists for nostr
which are optional for end users. There are other options such as the
"moderated communities" proposal which would provide tighter control.


On the user side, the optional moderation is very attractive, allowing
controversial threads to exist and continue, without requiring everyone to
see them.


The following do not currently exist (to my knowledge) and would need to be
implemented to meet the ML's requirements:

- an email gateway to satisfy the bulk of existing ML subscribers
  This reintroduces issues with mail server blocking of course.
- a long-form oriented nostr client (current plain text clients could be
used in the meantime)

That admittedly is quite a lot of work, but the second item can be
deferred, and the first is not particularly technically challenging, the
complications are all on the administration side.

I expect some reflexive NACKs based on the immaturity of the ecosystem but
if we have months to prepare, I believe the core requirements can be
solidly satisfied in time, the rest can be developed over time, and I
believe the advantages are worth careful consideration.

Cheers,
Dan

On Tue, Nov 7, 2023 at 9:38=E2=80=AFAM Bryan Bishop via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hello,
>
> We would like to request community feedback and proposals on the future o=
f
> the mailing list.
>
> Our current mailing list host, Linux Foundation, has indicated for years
> that they have wanted to stop hosting mailing lists, which would mean the
> bitcoin-dev mailing list would need to move somewhere else. We temporaril=
y
> avoided that, but recently LF has informed a moderator that they will cea=
se
> hosting any mailing lists later this year.
>
> In this email, we will go over some of the history, options, and invite
> discussion ahead of the cutoff. We have some ideas but want to solicit
> feedback and proposals.
>
> Background
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> The bitcoin-dev mailing list was originally hosted on Sourceforge.net. Th=
e
> bitcoin development mailing list has been a source of proposals, analysis=
,
> and developer discussion for many years in the bitcoin community, with ma=
ny
> thousands of participants. Later, the mailing list was migrated to the
> Linux Foundation, and after that OSUOSL began to help.
>
> Linux Foundation first asked us to move the mailing list in 2017. They
> internally attempted to migrate all LF mailing lists from mailman2 to
> mailman3, but ultimately gave up. There were reports of scalability issue=
s
> with mailman3 for large email communities. Ours definitely qualifies as..
> large.
>
> 2019 migration plan: LF was to turn off mailman and all lists would
> migrate to the paid service provider groups.io. Back then we were given
> accounts to try the groups.io interface and administration features.
> Apparently we were not the only dev community who resisted change. To our
> surprise LF gave us several years of reprieve by instead handing the
> subdomain and server-side data to the non-profit OSUOSL lab who instead
> operated mailman2 for the past ~4 years.
>
> OSUOSL has for decades been well known for providing server infrastructur=
e
> for Linux and Open Source development so they were a good fit. This howev=
er
> became an added maintenance burden for the small non-profit with limited
> resources. Several members of the Bitcoin dev community contributed fundi=
ng
> to the lab in support of their Open Source development infrastructure
> goals. But throwing money at the problem isn=E2=80=99t going to fix the o=
ngoing
> maintenance burden created by antiquated limitations of mailman2.
>
> Permalinks
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Linux Foundation has either offered or agreed to maintain archive
> permalinks so that content of historic importance is not lost. Fortunatel=
y
> for us while lists.linuxfoundation.org mailman will go down, they have
> agreed the read-only pipermail archives will remain online. So all old UR=
Ls
> will continue to remain valid. However, the moderators strongly advise th=
at
> the community supplements with public-inbox instances to have canonical
> archive urls that are separate from any particular email software host.
>
> Public-Inbox
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> https://public-inbox.org/README.html
>
> =E2=80=9CPublic Inbox=E2=80=9D decentralized archiving - no matter what m=
ailing list
> server solution is used, anyone can use git to maintain their own mailing
> list archive and make it available to read on the web.
>
> Public Inbox is a tool that you can run yourself. You can transform your
> mbox file and it makes it browsable and viewable online. It commits every
> post to a git repository. It's kind of like a decentralized mail archivin=
g
> tool. Anyone can publish the mail archive to any web server they wish.
>
> We should try to have one or more canonical archives that are served usin=
g
> public-inbox. But it doesn't matter if these are lost because anyone else
> can archive the mailing list in the same way and re-publish the archives.
>
> These git commits can also be stamped using opentimestamps, inserting
> their hashes into the bitcoin blockchain.
>
> LKML mailing list readers often use public-inbox's web interface, and the=
y
> use the reply-to headers to populate their mail client and reply to threa=
ds
> of interest. This allows their reply to be properly threaded even if they
> were not a previous subscriber to that mailing list to receive the header=
s.
>
> public-inbox makes it so that it doesn't really matter where the list is
> hosted, as pertaining to reading the mailing list. There is still a
> disruption if the mailing list goes away, but the archives live on and th=
en
> people can post elsewhere. The archive gets disconnected from the mailing
> list host in terms of posting. We could have a few canonical URLs for the
> hosts, separate from the mailing list server.
>
> mailman problems
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Over the years we have identified a number of problems with mailman2
> especially as it pertains to content moderation. There are presently a
> handful of different moderators, but mailman2 only has a single password
> for logging into the email management interface. There are no moderator
> audit logs to see which user (there is no concept of different users) act=
ed
> on an email. There is no way to mark an email as being investigated by on=
e
> or more of the moderators. Sometimes, while investigating the veracity of
> an email, another moderator would come in and approve a suspect email by
> accident.
>
> 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. The=
re
> is some support for filters in mailman2 but it's not great.
>
> 100% active moderation and approval of every email is unsustainable for
> volunteer moderators. A system that requires moderation is a heavy burden
> on the moderators and it slows down overall communication and productivit=
y.
> There's lots of problems with this. Also, moderators can be blamed when
> they are merely slow while they are not actually censoring.
>
> Rejection emails can optionally be sent to
> bitcoin-dev-moderation@lists.ozlabs.org but this is an option that a
> moderator has to remember to type in each time.
>
> Not to mention numerous bugs and vulnerabilities that have accumulated
> over the years for relatively unmaintained software. (Not disclosed here)
>
> Requirements and considerations
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
>
> Looking towards the future, there are a number of properties that seem to
> be important for the bitcoin-dev mailing list community. First, it is
> important that backups of the entire archive should be easy for the publi=
c
> to copy or verify so that the system can be brought up elsewhere if
> necessary.
>
> Second, there seems to be demand for both an email threading interface
> (using mailing list software) as well as web-accessible interfaces (such =
as
> forum software). There seems to be very few options that cater to both
> email and web. Often, in forum software, email support is limited to emai=
l
> notifications and there is limited if any support for email user
> participation.
>
> Third, there should be better support for moderator tools and management
> of the mailing list. See above for complaints about problems with the
> mailman2 system.
>
> Burdens of running your own mailing list and email server
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>
> If you have never operated your own MTA you have no idea how difficult it
> is to keep secure and functional in the face of numerous challenges to
> deliverability. Anti-spam filtering is essential to prevent forwarding
> spam. The moment you forward even a single spam message you run the risk =
of
> the server IP address being added to blacklists.
>
> The problem of spam filtering is so bad that most IP addresses are
> presumed guilty even if they have no prior spam history, such as if their
> network or subnetwork had spam issues in the past.
>
> Even if you put unlimited time into managing your own email server, other
> people may not accept your email. Or you make one mistake, and then you g=
et
> into permanent blacklists and it's hard to remove. The spam problem is so
> bad that most IPs are automatically on a guilty-until-proven-innocent
> blacklist.
>
> Often there is nothing you can do to get server IP addresses removed from
> spam blacklists or from "bad reputation" lists.
>
> Ironically, hashcash-style proof-of-work stamps to prevent spam are an
> appealing solution but not widely used in this community. Or anywhere.
>
> Infinite rejection or forwarding loops happen. They often need to be
> detected through vigilance and require manual sysadmin intervention to
> solve.
>
> Bitcoin's dev lists being hosted alongside other Open Source projects was
> previously protective. If that mailing list server became blacklisted the=
re
> were a lot of other people who would notice and complain. If we run a
> Bitcoin-specific mail server we are on our own. 100% of the administrativ=
e
> burden falls upon our own people. There is also nothing we can do if some
> unknown admin decides they don't like us.
>
> Options
> =3D=3D=3D=3D=3D=3D=3D
>
> Web forums are an interesting option, but often don't have good email use=
r
> integration. At most you can usually hope for email notifications and an
> ability to reply by email. It changes the model of the community from pus=
h
> (email) to pull (logging into a forum to read). RSS feeds can help a litt=
le
> bit.
>
> Many other projects have moved from mailing lists to forums (eg
> https://discuss.python.org/ =E2=80=93 see https://lwn.net/Articles/901744=
/ ; or
> https://ethresear.ch/), which seem easier to maintain and moderate, and
> can have lots of advanced features beyond plaintext, maybe-threading and
> maybe-HTML-markup.
>
> Who would host the forum? Would there be agreement around which forum
> software to use or which forum host? What about bitcointalk.org or
> delvingbitcoin.org? There are many options available. Maybe what we
> actually want isn=E2=80=99t so much a discussion forum, as an 'arxiv of o=
ur own'
> where anons can post BIP drafts and the like?
>
> Given the problems with mailman2, and the decline of email communities in
> general, it seems that moving to mailman3 would not be a viable long-term
> option. This leaves us with Google Groups or groups.io as two remaining
> options.
>
> groups.io is an interesting option: they are a paid service that
> implements email communities along with online web forum support. However=
,
> their public changelog indicates it has been a few years since their last
> public change. They might be a smaller company and it is unclear how long
> they will be around or if this would be the right fit for hosting sometim=
es
> contentious bitcoin development discussions...
>
> Google Groups is another interesting option, and comes with different
> tradeoffs. It's the lowest effort to maintain option, and has both an ema=
il
> interface and web forum interface. Users can choose which mode they want =
to
> interact with.
>
> For the Google Groups web interface, you can use it with a non-gmail
> account, but you must create a Google Account which is free to do. it doe=
s
> not require any personal information to do so. This also allows you to ad=
d
> 2FA. Non-gmail non-google users are able to subscribe and post email from
> their non-gmail non-google email accounts. Tor seems to work for the web
> interface.
>
> Will Google shut it down, will they cut us off, will they shut down
> non-google users? The same problem exists with other third-party hosts.
>
> The moderation capabilities for Google Groups and groups.io seem to be
> comparable. It seems more likely that Google Groups will be able to handl=
e
> email delivery issues far better than a small resource-constrained
> operation like groups.io. ((During feedback for this draft, luke-jr
> indicates that Google Workspaces has been known to use blacklisted IPs fo=
r
> business email!))
>
> On the other hand, groups.io is a paid service and you get what you pay
> for... hopefully?
>
> Finally, another option is to do literally nothing. It's less work
> overall. Users can switch to forums or other websites, or private
> one-on-one communication. It would remove a point of semi-centralization
> from the bitcoin ecosystem. It would hasten ossification, but on the othe=
r
> hand it would hasten ossification and this could be a negative too.
> Moderators would be less of a target.
>
> Unfortunately, by doing nothing, there would be no more widely used group
> email communication system between bitcoin developers. Developers become
> less coordinated, mayhem and chaos as people go to different communicatio=
n
> platforms, a divided community is more vulnerable, etc. BIP1 and BIP2 wou=
ld
> need to be revised for other venues.
>
> The main categories of what to move to are: web forums, mailing lists, an=
d
> hybrids of those two options. Most everything is either self-hosted or yo=
u
> pay someone else to host it. It's kind of the same problem though. It
> largely depends on how good is the software and unfortunately running you=
r
> own MTA that forwards mail is not a good option.
>
> Going forward
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> We'd like to invite feedback and proposals from the community, and see
> what options are available. One potential option is a migration to Google
> Groups, but we're open to ideas at this point. We apologize for any
> inconvenience this disruption has caused.
>
>
> Bitcoin-dev mailing list moderation team
>
> Bryan Bishop
> Ruben Somsen
> Warren Togami
> various others.
>
> --
> - Bryan
> https://twitter.com/kanzure
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--000000000000e08a66060992f3da
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Bryan,</div></div><div><br></div><div>I =
don&#39;t really want my first (and last?) devlist message to be a fairly o=
ff-the-cuff post on this topic, but here we go anyway.<br><div><br>At the r=
isk of sounding like a nostr evangelist (I promise I&#39;m not), I want to =
suggest nostr as a potential replacement to the mailing list. A decent chun=
k of software would need to be written, but none of the alternatives seem p=
articularly attractive to me. I particularly dislike the idea of locking in=
to a single siloed forum service like the bitcointalk forums. I realize I m=
ay be in the minority of course.</div><div><br></div><div><br></div>Nostr e=
nables the ML team to outsource all of its biggest burdens, if it chooses:<=
br><div><br></div><div>- mail server blocking is N/A to nostr</div><br>- Ho=
sting costs are completely outsourced unless the ML team chooses to host a =
relay.<br><div><br></div>- Archives and web portal access can be similarly =
outsourced because any nostr archive is self-authenticating.<br><br></div><=
div>- The ML team can also choose to completely outsource moderation, as no=
str is (more or less) permissionless by nature.<br></div><div>=C2=A0 I unde=
rstand if there is a &quot;blessed&quot; communication system, the ML team =
would probably prefer to keep it high quality. To that end there are propos=
als for proof-of-work, and web of trust based blocklists for nostr which ar=
e optional for end users. There are other options such as the &quot;moderat=
ed communities&quot; proposal which would provide tighter control.<br></div=
><br><div><br></div><div>On the user side, the optional moderation is very =
attractive, allowing controversial threads to exist and continue, without r=
equiring everyone to see them.<br><br></div><div><br></div><div>The followi=
ng do not currently exist (to my knowledge) and would need to be implemente=
d to meet the ML&#39;s requirements:<br><br>- an email gateway to satisfy t=
he bulk of existing ML subscribers</div><div>=C2=A0 This reintroduces issue=
s with mail server blocking of course.<br></div><div>- a long-form oriented=
 nostr client (current plain text clients could be used in the meantime)<br=
><br></div><div>That admittedly is quite a lot of work, but the second item=
 can be deferred, and the first is not particularly technically challenging=
, the complications are all on the administration side.<br><br></div><div>I=
 expect some reflexive NACKs based on the immaturity of the ecosystem but i=
f we have months to prepare, I believe the core requirements can be solidly=
 satisfied in time, the rest can be developed over time, and I believe the =
advantages are worth careful consideration.<br></div></div><div><br></div><=
div>Cheers,</div><div>Dan</div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Tue, Nov 7, 2023 at 9:38=E2=80=AFAM Bryan=
 Bishop via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfounda=
tion.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hello,<br><=
br>We would like to request community=C2=A0feedback and proposals on the fu=
ture of the mailing list.<div><br><div>Our current mailing list host, Linux=
 Foundation, has indicated for years that they have wanted to stop hosting =
mailing lists, which would mean the bitcoin-dev mailing list would need to =
move somewhere else. We temporarily avoided that, but recently LF has infor=
med a moderator that they will cease hosting any mailing lists later this y=
ear.</div><div><br>In this email, we will go over some of the history, opti=
ons, and invite discussion ahead of the cutoff. We have some ideas but want=
 to solicit feedback and proposals.<br><br>Background<br>=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br><br>The bitcoin-dev mailing list was originally hosted on S=
ourceforge.net. The bitcoin development mailing list has been a source of p=
roposals, analysis, and developer discussion for many years in the bitcoin =
community, with many thousands of participants. Later, the mailing list was=
 migrated to the Linux Foundation, and after that OSUOSL began to help.<br>=
<br>Linux Foundation first asked us to move the mailing list in 2017. They =
internally attempted to migrate all LF mailing lists from mailman2 to mailm=
an3, but ultimately gave up. There were reports of scalability issues with =
mailman3 for large email communities. Ours definitely qualifies as.. large.=
<br><br>2019 migration plan: LF was to turn off mailman and all lists would=
 migrate to the paid service provider <a href=3D"http://groups.io" target=
=3D"_blank">groups.io</a>. Back then we were given accounts to try the <a h=
ref=3D"http://groups.io" target=3D"_blank">groups.io</a> interface and admi=
nistration features. Apparently we were not the only dev community who resi=
sted change. To our surprise LF gave us several years of reprieve by instea=
d handing the subdomain and server-side data to the non-profit OSUOSL lab w=
ho instead operated mailman2 for the past ~4 years.<br><br>OSUOSL has for d=
ecades been well known for providing server infrastructure for Linux and Op=
en Source development so they were a good fit. This however became an added=
 maintenance burden for the small non-profit with limited resources. Severa=
l members of the Bitcoin dev community contributed funding to the lab in su=
pport of their Open Source development infrastructure goals. But throwing m=
oney at the problem isn=E2=80=99t going to fix the ongoing maintenance burd=
en created by antiquated limitations of mailman2.<br><br>Permalinks<br>=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>Linux Foundation has either offered or a=
greed to maintain archive permalinks so that content of historic importance=
 is not lost. Fortunately for us while <a href=3D"http://lists.linuxfoundat=
ion.org" target=3D"_blank">lists.linuxfoundation.org</a> mailman will go do=
wn, they have agreed the read-only pipermail archives will remain online. S=
o all old URLs will continue to remain valid. However, the moderators stron=
gly advise that the community supplements with public-inbox instances to ha=
ve canonical archive urls that are separate from any particular email softw=
are host.<br><br>Public-Inbox<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><b=
r><a href=3D"https://public-inbox.org/README.html" target=3D"_blank">https:=
//public-inbox.org/README.html</a><br><br>=E2=80=9CPublic Inbox=E2=80=9D de=
centralized archiving - no matter what mailing list server solution is used=
, anyone can use git to maintain their own mailing list archive and make it=
 available to read on the web.<br><br>Public Inbox is a tool that you can r=
un yourself. You can transform your mbox file and it makes it browsable and=
 viewable online. It commits every post to a git repository. It&#39;s kind =
of like a decentralized mail archiving tool. Anyone can publish the mail ar=
chive to any web server they wish.<br><br>We should try to have one or more=
 canonical archives that are served using public-inbox. But it doesn&#39;t =
matter if these are lost because anyone else can archive the mailing list i=
n the same way and re-publish the archives.<br><br>These git commits can al=
so be stamped using opentimestamps, inserting their hashes into the bitcoin=
 blockchain.<br><br>LKML mailing list readers often use public-inbox&#39;s =
web interface, and they use the reply-to headers to populate their mail cli=
ent and reply to threads of interest. This allows their reply to be properl=
y threaded even if they were not a previous subscriber to that mailing list=
 to receive the headers.<br><br>public-inbox makes it so that it doesn&#39;=
t really matter where the list is hosted, as pertaining to reading the mail=
ing list. There is still a disruption if the mailing list goes away, but th=
e archives live on and then people can post elsewhere. The archive gets dis=
connected from the mailing list host in terms of posting. We could have a f=
ew canonical URLs for the hosts, separate from the mailing list server.<br>=
<br>mailman problems<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
><br>Over the years we have identified a number of problems with mailman2 e=
specially as it pertains to content moderation. There are presently a handf=
ul of different moderators, but mailman2 only has a single password for log=
ging into the email management interface. There are no moderator audit logs=
 to see which user (there is no concept of different users) acted on an ema=
il. There is no way to mark an email as being investigated by one or more o=
f the moderators. Sometimes, while investigating the veracity of an email, =
another moderator would come in and approve a suspect email by accident.<br=
><br>Anti spam has been an issue for the moderators. It&#39;s relentless. W=
ithout access to the underlying server, it has been difficult to fight spam=
. There is some support for filters in mailman2 but it&#39;s not great.<br>=
<br>100% active moderation and approval of every email is unsustainable for=
 volunteer moderators. A system that requires moderation is a heavy burden =
on the moderators and it slows down overall communication and productivity.=
 There&#39;s lots of problems with this. Also, moderators can be blamed whe=
n they are merely slow while they are not actually censoring.<br><br>Reject=
ion emails can optionally be sent to <a href=3D"mailto:bitcoin-dev-moderati=
on@lists.ozlabs.org" target=3D"_blank">bitcoin-dev-moderation@lists.ozlabs.=
org</a> but this is an option that a moderator has to remember to type in e=
ach time.<br><br>Not to mention numerous bugs and vulnerabilities that have=
 accumulated over the years for relatively unmaintained software. (Not disc=
losed here)<br><br>Requirements and considerations<br>=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
><br>Looking towards the future, there are a number of properties that seem=
 to be important for the bitcoin-dev mailing list community. First, it is i=
mportant that backups of the entire archive should be easy for the public t=
o copy or verify so that the system can be brought up elsewhere if necessar=
y.<br><br>Second, there seems to be demand for both an email threading inte=
rface (using mailing list software) as well as web-accessible interfaces (s=
uch as forum software). There seems to be very few options that cater to bo=
th email and web. Often, in forum software, email support is limited to ema=
il notifications and there is limited if any support for email user partici=
pation.<br><br>Third, there should be better support for moderator tools an=
d management of the mailing list. See above for complaints about problems w=
ith the mailman2 system.<br><br>Burdens of running your own mailing list an=
d email server<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>If you have never operated y=
our own MTA you have no idea how difficult it is to keep secure and functio=
nal in the face of numerous challenges to deliverability. Anti-spam filteri=
ng is essential to prevent forwarding spam. The moment you forward even a s=
ingle spam message you run the risk of the server IP address being added to=
 blacklists.<br><br>The problem of spam filtering is so bad that most IP ad=
dresses are presumed guilty even if they have no prior spam history, such a=
s if their network or subnetwork had spam issues in the past.<br><br>Even i=
f you put unlimited time into managing your own email server, other people =
may not accept your email. Or you make one mistake, and then you get into p=
ermanent blacklists and it&#39;s hard to remove. The spam problem is so bad=
 that most IPs are automatically on a guilty-until-proven-innocent blacklis=
t.<br><br>Often there is nothing you can do to get server IP addresses remo=
ved from spam blacklists or from &quot;bad reputation&quot; lists.<br><br>I=
ronically, hashcash-style proof-of-work stamps to prevent spam are an appea=
ling solution but not widely used in this community. Or anywhere.<br><br>In=
finite rejection or forwarding loops happen. They often need to be detected=
 through vigilance and require manual sysadmin intervention to solve.<br><b=
r>Bitcoin&#39;s dev lists being hosted alongside other Open Source projects=
 was previously protective. If that mailing list server became blacklisted =
there were a lot of other people who would notice and complain. If we run a=
 Bitcoin-specific mail server we are on our own. 100% of the administrative=
 burden falls upon our own people. There is also nothing we can do if some =
unknown admin decides they don&#39;t like us.<br><br>Options<br>=3D=3D=3D=
=3D=3D=3D=3D<br><br>Web forums are an interesting option, but often don&#39=
;t have good email user integration. At most you can usually hope for email=
 notifications and an ability to reply by email. It changes the model of th=
e community from push (email) to pull (logging into a forum to read). RSS f=
eeds can help a little bit.<br><br>Many other projects have moved from mail=
ing lists to forums (eg <a href=3D"https://discuss.python.org/" target=3D"_=
blank">https://discuss.python.org/</a> =E2=80=93 see <a href=3D"https://lwn=
.net/Articles/901744/" target=3D"_blank">https://lwn.net/Articles/901744/</=
a> ; or <a href=3D"https://ethresear.ch/" target=3D"_blank">https://ethrese=
ar.ch/</a>), which seem easier to maintain and moderate, and can have lots =
of advanced features beyond plaintext, maybe-threading and maybe-HTML-marku=
p.<br><br>Who would host the forum? Would there be agreement around which f=
orum software to use or which forum host? What about <a href=3D"http://bitc=
ointalk.org" target=3D"_blank">bitcointalk.org</a> or <a href=3D"http://del=
vingbitcoin.org" target=3D"_blank">delvingbitcoin.org</a>? There are many o=
ptions available. Maybe what we actually want isn=E2=80=99t so much a discu=
ssion forum, as an &#39;arxiv of our own&#39; where anons can post BIP draf=
ts and the like?<br><br>Given the problems with mailman2, and the decline o=
f email communities in general, it seems that moving to mailman3 would not =
be a viable long-term option. This leaves us with Google Groups or <a href=
=3D"http://groups.io" target=3D"_blank">groups.io</a> as two remaining opti=
ons.<br><br><a href=3D"http://groups.io" target=3D"_blank">groups.io</a> is=
 an interesting option: they are a paid service that implements email commu=
nities along with online web forum support. However, their public changelog=
 indicates it has been a few years since their last public change. They mig=
ht be a smaller company and it is unclear how long they will be around or i=
f this would be the right fit for hosting sometimes contentious bitcoin dev=
elopment discussions...<br><br>Google Groups is another interesting option,=
 and comes with different tradeoffs. It&#39;s the lowest effort to maintain=
 option, and has both an email interface and web forum interface. Users can=
 choose which mode they want to interact with.<br><br>For the Google Groups=
 web interface, you can use it with a non-gmail account, but you must creat=
e a Google Account which is free to do. it does not require any personal in=
formation to do so. This also allows you to add 2FA. Non-gmail non-google u=
sers are able to subscribe and post email from their non-gmail non-google e=
mail accounts. Tor seems to work for the web interface. <br><br>Will Google=
 shut it down, will they cut us off, will they shut down non-google users? =
The same problem exists with other third-party hosts.<br><br>The moderation=
 capabilities for Google Groups and <a href=3D"http://groups.io" target=3D"=
_blank">groups.io</a> seem to be comparable. It seems more likely that Goog=
le Groups will be able to handle email delivery issues far better than a sm=
all resource-constrained operation like <a href=3D"http://groups.io" target=
=3D"_blank">groups.io</a>. ((During feedback for this draft, luke-jr indica=
tes that Google Workspaces has been known to use blacklisted IPs for busine=
ss email!))<br><br>On the other hand, <a href=3D"http://groups.io" target=
=3D"_blank">groups.io</a> is a paid service and you get what you pay for...=
 hopefully?<br><br>Finally, another option is to do literally nothing. It&#=
39;s less work overall. Users can switch to forums or other websites, or pr=
ivate one-on-one communication. It would remove a point of semi-centralizat=
ion from the bitcoin ecosystem. It would hasten ossification, but on the ot=
her hand it would hasten ossification and this could be a negative too. Mod=
erators would be less of a target.<br><br>Unfortunately, by doing nothing, =
there would be no more widely used group email communication system between=
 bitcoin developers. Developers become less coordinated, mayhem and chaos a=
s people go to different communication platforms, a divided community is mo=
re vulnerable, etc. BIP1 and BIP2 would need to be revised for other venues=
.<br><br>The main categories of what to move to are: web forums, mailing li=
sts, and hybrids of those two options. Most everything is either self-hoste=
d or you pay someone else to host it. It&#39;s kind of the same problem tho=
ugh. It largely depends on how good is the software and unfortunately runni=
ng your own MTA that forwards mail is not a good option.<br><br>Going forwa=
rd<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>We&#39;d like to invite feed=
back and proposals from the community, and see what options are available. =
One potential option is a migration to Google Groups, but we&#39;re open to=
 ideas at this point. We apologize for any inconvenience this disruption ha=
s caused.<br><br><br>Bitcoin-dev mailing list moderation team<br><br>Bryan =
Bishop<br>Ruben Somsen<br>Warren Togami<br>various others.<br><div><br></di=
v><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" cla=
ss=3D"gmail_signature"><div dir=3D"ltr">- Bryan<br><a href=3D"https://twitt=
er.com/kanzure" target=3D"_blank">https://twitter.com/kanzure</a></div></di=
v></div></div></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000e08a66060992f3da--