From: "David A. Harding" <dave@dtrt•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, 07 Nov 2023 10:07:38 -1000 [thread overview]
Message-ID: <a79e338fab982da901eb15379ee79150@dtrt.org> (raw)
In-Reply-To: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
On 2023-11-07 05:37, Bryan Bishop via bitcoin-dev wrote:
> What about [...] delvingbitcoin.org?
I'm only willing to consider discussion groups that provide good
archives, so I think it's worth noting that James O'Beirne has written
code[1] and is currently maintaining a git repo[2] with a backup of
Delving Bitcoin discussion. See his post[3] for additional details.
In addition to providing an archive, I currently find it to be nice way
to quickly skim all posts made to the forum since I last checked (plus I
see edits)[4]:
$ cd delving-bitcoin-archive/
$ git pull
$ git log -p archive/rendered-topics/
I think some technical discussions were already migrating to Delving
Bitcoin before the shutdown notice and I expect more discussions to move
there in the future even if the current mailing list is relocated to a
new platform. Knowing that discussions are archived in a way that I can
easily replicate was key to me feeling comfortable putting significant
time into reading and writing posts on Delving Bitcoin, so I wanted to
share that information here.
-Dave
[1] https://github.com/jamesob/discourse-archive
[2] https://github.com/jamesob/delving-bitcoin-archive
[3] https://delvingbitcoin.org/t/public-archive-for-delving-bitcoin/87/6
[4] Plus every commit makes me laugh. James O'Beirne's commit robot is
called "jamesobot"
next prev parent reply other threads:[~2023-11-07 20:07 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 [this message]
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
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=a79e338fab982da901eb15379ee79150@dtrt.org \
--to=dave@dtrt$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kanzure@gmail$(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