MIME-Version: 1.0
References: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>
 <a79e338fab982da901eb15379ee79150@dtrt.org>
In-Reply-To: <a79e338fab982da901eb15379ee79150@dtrt.org>
From: Keagan McClelland <keagan.mcclelland@gmail.com>
Date: Tue, 7 Nov 2023 13:03:09 -0800
Message-ID: <CALeFGL1_6CkJvv+ftGeh8A3j_R5Feg5QnnAzE2bh0zexufgp0Q@mail.gmail.com>
To: "David A. Harding" <dave@dtrt.org>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000ee75620609964c6e"
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
Precedence: list

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

I also think that good archives are extremely important. Far more important
than being a medium of discussion is capturing all of that discussion for
posterity. An unbelievable amount of knowledge capital has been built up in
the mailing list over the years and given that Bitcoin is a system that
needs to survive complete turnover in its contributor base, it's of extreme
importance that we have a system that can capture the archive.

While Nostr might be good towards the end of being very resilient it isn't
mature enough to have good UX's built up around it wherein people with a
variety of backgrounds can engage it. Personally, I think the email UX
leaves a lot to be desired but at least it's accessible to a lot of people.
I don't think I can say the same for Nostr yet.

I won't opine much further on the solution but I think the properties we
need to solve for are:

1. Archive is effectively permanent
2. Accessible to a wide audience
3. Data format is not proprietary and isn't tied to the success or failure
of a particular organization

In principle I think that Nostr can offer a lot in the long term towards
this goal, but it isn't really an immediate solution to this problem.

Keags

On Tue, Nov 7, 2023 at 12:07=E2=80=AFPM David A. Harding via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> 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"
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div>I also think that good archives are extremely importa=
nt. Far more important than being a medium of discussion is capturing all o=
f that discussion for posterity. An unbelievable amount of knowledge capita=
l has been built up in the mailing list over the years and given that Bitco=
in is a system that needs to survive complete turnover in its contributor b=
ase, it&#39;s of extreme importance that we have a system that can capture =
the archive.</div><div><br></div><div>While Nostr might be good towards the=
 end of being very resilient it isn&#39;t mature enough to have good UX&#39=
;s built up around it wherein people with a variety of backgrounds can enga=
ge it. Personally, I think the email UX leaves a lot to be desired but at l=
east it&#39;s accessible to a lot of people. I don&#39;t think I can say th=
e same for Nostr yet.<br></div><div><br></div><div>I won&#39;t opine much f=
urther on the solution but I think the properties we need to solve for are:=
</div><div><br></div><div>1. Archive is effectively permanent</div><div>2. =
Accessible to a wide audience</div><div>3. Data format is not proprietary a=
nd isn&#39;t tied to the success or failure of a particular organization</d=
iv><div><br></div><div>In principle I think that Nostr can offer a lot in t=
he long term towards this goal, but it isn&#39;t really an immediate soluti=
on to this problem.</div><div><br></div><div>Keags</div></div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 7, 2023=
 at 12:07=E2=80=AFPM David A. Harding via bitcoin-dev &lt;<a href=3D"mailto=
:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.o=
rg</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">On 2023-11-07 05:37, Bryan Bishop via bitcoin-dev wrote:<br>
&gt; What about [...] <a href=3D"http://delvingbitcoin.org" rel=3D"noreferr=
er" target=3D"_blank">delvingbitcoin.org</a>?<br>
<br>
I&#39;m only willing to consider discussion groups that provide good <br>
archives, so I think it&#39;s worth noting that James O&#39;Beirne has writ=
ten <br>
code[1] and is currently maintaining a git repo[2] with a backup of <br>
Delving Bitcoin discussion.=C2=A0 See his post[3] for additional details.<b=
r>
<br>
In addition to providing an archive, I currently find it to be nice way <br=
>
to quickly skim all posts made to the forum since I last checked (plus I <b=
r>
see edits)[4]:<br>
<br>
$ cd delving-bitcoin-archive/<br>
$ git pull<br>
$ git log -p archive/rendered-topics/<br>
<br>
I think some technical discussions were already migrating to Delving <br>
Bitcoin before the shutdown notice and I expect more discussions to move <b=
r>
there in the future even if the current mailing list is relocated to a <br>
new platform.=C2=A0 Knowing that discussions are archived in a way that I c=
an <br>
easily replicate was key to me feeling comfortable putting significant <br>
time into reading and writing posts on Delving Bitcoin, so I wanted to <br>
share that information here.<br>
<br>
-Dave<br>
<br>
[1] <a href=3D"https://github.com/jamesob/discourse-archive" rel=3D"norefer=
rer" target=3D"_blank">https://github.com/jamesob/discourse-archive</a><br>
[2] <a href=3D"https://github.com/jamesob/delving-bitcoin-archive" rel=3D"n=
oreferrer" target=3D"_blank">https://github.com/jamesob/delving-bitcoin-arc=
hive</a><br>
[3] <a href=3D"https://delvingbitcoin.org/t/public-archive-for-delving-bitc=
oin/87/6" rel=3D"noreferrer" target=3D"_blank">https://delvingbitcoin.org/t=
/public-archive-for-delving-bitcoin/87/6</a><br>
[4] Plus every commit makes me laugh.=C2=A0 James O&#39;Beirne&#39;s commit=
 robot is <br>
called &quot;jamesobot&quot;<br>
_______________________________________________<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>

--000000000000ee75620609964c6e--