From: Anthony Towns <aj@erisian•com.au>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
Date: Wed, 8 Nov 2023 13:56:17 +1000 [thread overview]
Message-ID: <ZUsG4fxgrdCIulef@erisian.com.au> (raw)
In-Reply-To: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
On Tue, Nov 07, 2023 at 09:37:22AM -0600, Bryan Bishop via bitcoin-dev wrote:
> Web forums are an interesting option, but often don't have good email user
> integration.
> What about bitcointalk.org or delvingbitcoin.org?
delvingbitcoin.org is something I setup; it's a self-hosted discourse
instance. (You don't have to self-host discourse, but not doing so limits
the number of admins/moderators, the plugins you can use, and the APIs you
can access)
For what it's worth, I think (discourse) forums have significant
advantages over email for technical discussion:
* much better markup: you can write LaTeX for doing maths, you
can have graphviz or mermaid diagrams generated directly from text,
you can do formatting without having to worry about HTML email.
because that's done direct from markup, you can also quote such
things in replies, or easily create a modified equation/diagram
if desired, things that are much harder if equations/diagrams are
image/pdf attachments.
* consistent threading/quoting: you don't have to rely on email clients
to get threading/quoting correct in order to link replies with the
original message
* having topics/replies, rather than everything being an individual
email, tends to make it easier to avoid being distracted by followups
to a topic you're not interested in.
* you can do reactions (heart / thumbs up / etc) instead of "me too"
posts, minimising the impact of low-content responses on readers,
without doing away with those responses entirely.
* after the fact moderation: with mailing lists, moderation can only
be a choice between "send this post to every subscriber" or not,
and the choice obviously has to be made before anyone sees the posts;
forums allow off-topic/unconstructive posts to be removed or edited.
Compared to mailing-lists-as-a-service, a self-hosted forum has a few
other possible benefits:
* it's easier to setup areas for additional topics, without worrying
you're going to be forced into an arbitrarily higher pricing tier
* you can setup spaces for private working groups. (and those groups can
make their internal discussions public after the fact, if desired)
* you can use plugin interfaces/APIs to link up with external resources
There are a few disadvantages too:
* discourse isn't lightweight -- you need a whole bunch of infrastructure
to go from the markdown posts to the actual rendered posts/comments;
so backups of just the markdown text isn't really "complete"
* discourse is quite actively developed -- so it could be possible
that posts that use particular features/plugins (eg to generate
diagrams) will go stale eventually as the software changes, and stop
being rendered correctly
* discourse gathers a moderate amount of non-public/potentially private
data (eg email addresses, passwords, IP addresses, login times) that
may make backups and admin access sensitive (which is why there's a
git archive generated by a bot for delvingbitcoin, rather than raw
database dumps)
There are quite a few open source projects using discourse instances, eg:
Python: https://discuss.python.org/
Ruby on Rails: https://discuss.rubyonrails.org/
LLVM: https://discourse.llvm.org/
Jupyter: https://discourse.jupyter.org/
Fedora: https://discussion.fedoraproject.org/
Ubuntu: https://discourse.ubuntu.com/
Haskell: https://discourse.haskell.org/
There's also various crypto projects using it:
Eth research: https://ethresear.ch/
Chia: https://developers.chia.net/
There's a couple of LWN articles on Python's adoption of discourse
that I found interesting, fwiw:
https://lwn.net/Articles/901744/ [2022-07-20]
https://lwn.net/Articles/674271/ [2016-02-03]
I don't think this needs to be an "either-or" question -- better to
have technical discussions about bitcoin in many places and in many
formats, rather than just one -- but I thought I'd take the opportunity
to write out why I thought discourse was worth spending some time on in
this context.
Cheers,
aj
next prev parent reply other threads:[~2023-11-08 3:56 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 [this message]
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=ZUsG4fxgrdCIulef@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--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