Delivery-date: Fri, 09 Feb 2024 12:35:28 -0800
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of kanzure@gmail.com designates 2a00:1450:4864:20::532 as permitted sender) client-ip=2a00:1450:4864:20::532;
MIME-Version: 1.0
References: <CABaSBayz8UxiJS30BUNntp2JtzJMP4rsGfQqtvbbts5MK3MPLw@mail.gmail.com>
In-Reply-To: <CABaSBayz8UxiJS30BUNntp2JtzJMP4rsGfQqtvbbts5MK3MPLw@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
Date: Fri, 9 Feb 2024 14:34:44 -0600
Message-ID: <CABaSBaxDjj6ySBx4v+rmpfrw4pE9b=JZJPzPQj_ZUiBg1HGFyA@mail.gmail.com>
Subject: [bitcoindev] bitcoin-dev Mailing List Migration (Action Required)
To: bitcoindev@googlegroups.com
Content-Type: multipart/alternative; boundary="0000000000007be8ff0610f8dc6d"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

--0000000000007be8ff0610f8dc6d
Content-Type: text/plain; charset="UTF-8"

Recently we announced a forthcoming mailing list migration. We are now
ready to announce details.

After working through a few roadblocks we are now finally ready to migrate
the mailing list to Google Groups. Emails to the old list are no longer
accepted as of February 2024. Subscribe promptly to ensure you're not
missing any emails. We'll wait 24 hours prior to letting new emails through
to give people time to subscribe.

The new location of the bitcoindev mailing list is:
https://groups.google.com/group/bitcoindev

Ongoing archive including previous messages:
https://gnusha.org/pi/bitcoindev

If you want to subscribe manually you have two options. You can send an
email to bitcoindev+subscribe@googlegroups.com and then send a reply to the
automated email you'll receive (check your spam folder). Alternatively, you
can also subscribe through the online interface at
https://groups.google.com/g/bitcoindev, using a Google account (not the
same as gmail - you can create a Google account with any email address you
like).

We encourage everyone to stay opted in to receiving *all* messages,
especially if you want to actively participate in the conversation. If you
don't do this, you won't be able to reply to existing messages easily,
which commonly breaks threading and inconveniences readers. In order to
keep your main inbox uncluttered, you can set up a filter for messages that
have bitcoindev@googlegroups.com as the recipient.

The new mailing list archive can be viewed in the online interface (no
Google account required) and is also backed up externally at
https://gnusha.org/pi/bitcoindev. The old mailing list contents can also be
viewed there. Note we aren't relying on Google for anything critical here
and are merely using them as a conduit for information that is already
meant to be public.

We would like to encourage others to host public archives of the mailing
list in addition to the gnusha.org/pi/bitcoindev public-inbox archive. With
the public-inbox.org-based archive, it's as simple as git cloning,
subscribing (using bitcoindev+subscribe@googlegroups.com and then replying
to bitcoindev+subconfirm@googlegroups.com) and configuring your own
public-inbox instance, or any other mail archive that you prefer. Once you
set up an archive, send us a message and let us know where users can view
it.

A comprehensive archive of the bitcoin-dev mailing list, as part of the
migration away from the previous server(s), and as part of the creation of
the public-inbox archive, can be found here (see README inside for more
details):
https://diyhpl.us/~bryan/irc/bitcoin/bitcoin-dev/bitcoin-dev-ml-archive.2024-02-09-004.tar.gz
https://diyhpl.us/~bryan/irc/bitcoin/bitcoin-dev/bitcoin-dev-ml-archive.2024-02-09-004.tar.gz.ots
sha256: 86b8fb99451f990adbe755a1c363d9814ae620255d8fed5b4f7b0d4d59430b3c
sha512:
1611215fd87e40ba36cde8cb39a228497139ea10fb5cdec7d41c0af9b1b91c8860199dc7ba8d6d75fe249c4d4d434f087b3528c687ab02e6b231b29650aef5ff

Finally, we'd like to remind people that mailing lists are essentially a
mass broadcast medium with only very limited moderation options. Please try
to think about whether your post is relevant to everyone, especially when
starting a new topic, in order to maintain a decent signal-to-noise ratio.
The rules remain unchanged and can be viewed at
https://groups.google.com/g/bitcoindev/about.

Moderators can be reached at bitcoindev+owner@googlegroups.com.

On behalf of the mailing list moderation team, thank you for bearing with
us. We would also like to thank Joe Rayhawk <jrayhawk@fairlystable.org> for
his assistance with software and infrastructure configuration during this
migration.

Ruben Somsen
Bryan Bishop
Warren Togami

previous communication on this matter:
https://gnusha.org/pi/bitcoindev/CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com/


- Bryan
https://twitter.com/kanzure

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/CABaSBaxDjj6ySBx4v%2Brmpfrw4pE9b%3DJZJPzPQj_ZUiBg1HGFyA%40mail.gmail.com.

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">Recently we an=
nounced a forthcoming mailing list migration. We are now ready to announce =
details.<br><br>After working through a few roadblocks we are now finally r=
eady to migrate the mailing list to Google Groups. Emails to the old list a=
re no longer accepted as of February 2024. Subscribe promptly to ensure you=
&#39;re not missing any emails. We&#39;ll wait 24 hours prior to letting ne=
w emails through to give people time to subscribe.<br><br>The new location =
of the bitcoindev mailing list is:<br><a href=3D"https://groups.google.com/=
group/bitcoindev" target=3D"_blank">https://groups.google.com/group/bitcoin=
dev</a><br><br>Ongoing archive including previous messages:<br><a href=3D"h=
ttps://gnusha.org/pi/bitcoindev" target=3D"_blank">https://gnusha.org/pi/bi=
tcoindev</a><br><br>If you want to subscribe manually you have two options.=
 You can send an email to <a href=3D"mailto:bitcoindev%2Bsubscribe@googlegr=
oups.com" target=3D"_blank">bitcoindev+subscribe@googlegroups.com</a> and t=
hen send a reply to the automated email you&#39;ll receive (check your spam=
 folder). Alternatively, you can also subscribe through the online interfac=
e at <a href=3D"https://groups.google.com/g/bitcoindev" target=3D"_blank">h=
ttps://groups.google.com/g/bitcoindev</a>, using a Google account (not the =
same as gmail - you can create a Google account with any email address you =
like). <br><br>We encourage everyone to stay opted in to receiving *all* me=
ssages, especially if you want to actively participate in the conversation.=
 If you don&#39;t do this, you won&#39;t be able to reply to existing messa=
ges easily, which commonly breaks threading and inconveniences readers. In =
order to keep your main inbox uncluttered, you can set up a filter for mess=
ages that have <a href=3D"mailto:bitcoindev@googlegroups.com" target=3D"_bl=
ank">bitcoindev@googlegroups.com</a> as the recipient.<br><br>The new maili=
ng list archive can be viewed in the online interface (no Google account re=
quired) and is also backed up externally at <a href=3D"https://gnusha.org/p=
i/bitcoindev" target=3D"_blank">https://gnusha.org/pi/bitcoindev</a>. The o=
ld mailing list contents can also be viewed there. Note we aren&#39;t relyi=
ng on Google for anything critical here and are merely using them as a cond=
uit for information that is already meant to be public.<br><br>We would lik=
e to encourage others to host public archives of the mailing list in additi=
on to the <a href=3D"http://gnusha.org/pi/bitcoindev" target=3D"_blank">gnu=
sha.org/pi/bitcoindev</a> public-inbox archive. With the public-inbox.org-b=
ased archive, it&#39;s as simple as git cloning, subscribing (using <a href=
=3D"mailto:bitcoindev%2Bsubscribe@googlegroups.com" target=3D"_blank">bitco=
indev+subscribe@googlegroups.com</a> and then replying to <a href=3D"mailto=
:bitcoindev%2Bsubconfirm@googlegroups.com" target=3D"_blank">bitcoindev+sub=
confirm@googlegroups.com</a>) and configuring your own public-inbox instanc=
e, or any other mail archive that you prefer. Once you set up an archive, s=
end us a message and let us know where users can view it.<br><br>A comprehe=
nsive archive of the bitcoin-dev mailing list, as part of the migration awa=
y from the previous server(s), and as part of the creation of the public-in=
box archive, can be found here (see README inside for more details):<br><a =
href=3D"https://diyhpl.us/~bryan/irc/bitcoin/bitcoin-dev/bitcoin-dev-ml-arc=
hive.2024-02-09-004.tar.gz" target=3D"_blank">https://diyhpl.us/~bryan/irc/=
bitcoin/bitcoin-dev/bitcoin-dev-ml-archive.2024-02-09-004.tar.gz</a><br><a =
href=3D"https://diyhpl.us/~bryan/irc/bitcoin/bitcoin-dev/bitcoin-dev-ml-arc=
hive.2024-02-09-004.tar.gz.ots" target=3D"_blank">https://diyhpl.us/~bryan/=
irc/bitcoin/bitcoin-dev/bitcoin-dev-ml-archive.2024-02-09-004.tar.gz.ots</a=
><br>sha256: 86b8fb99451f990adbe755a1c363d9814ae620255d8fed5b4f7b0d4d59430b=
3c<br>sha512: 1611215fd87e40ba36cde8cb39a228497139ea10fb5cdec7d41c0af9b1b91=
c8860199dc7ba8d6d75fe249c4d4d434f087b3528c687ab02e6b231b29650aef5ff<br><br>=
Finally, we&#39;d like to remind people that mailing lists are essentially =
a mass broadcast medium with only very limited moderation options. Please t=
ry to think about whether your post is relevant to everyone, especially whe=
n starting a new topic, in order to maintain a decent signal-to-noise ratio=
. The rules remain unchanged and can be viewed at <a href=3D"https://groups=
.google.com/g/bitcoindev/about" target=3D"_blank">https://groups.google.com=
/g/bitcoindev/about</a>.<br><br>Moderators can be reached at <a href=3D"mai=
lto:bitcoindev%2Bowner@googlegroups.com" target=3D"_blank">bitcoindev+owner=
@googlegroups.com</a>.<br><br>On behalf of the mailing list moderation team=
, thank you for bearing with us. We would also like to thank Joe Rayhawk &l=
t;<a href=3D"mailto:jrayhawk@fairlystable.org" target=3D"_blank">jrayhawk@f=
airlystable.org</a>&gt; for his assistance with software and infrastructure=
 configuration during this migration.<br><br>Ruben Somsen<br>Bryan Bishop<b=
r>Warren Togami<br><br>previous communication on this matter: <a href=3D"ht=
tps://gnusha.org/pi/bitcoindev/CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGV=
B=3DzhdwQ@mail.gmail.com/" target=3D"_blank">https://gnusha.org/pi/bitcoind=
ev/CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=3DzhdwQ@mail.gmail.com/</a=
><br clear=3D"all"><div><br></div><br><div dir=3D"ltr" class=3D"gmail_signa=
ture" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">- Bryan<br><a hre=
f=3D"https://twitter.com/kanzure" target=3D"_blank">https://twitter.com/kan=
zure</a></div></div></div></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/CABaSBaxDjj6ySBx4v%2Brmpfrw4pE9b%3DJZJPzPQj_ZUiBg1HGF=
yA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.=
google.com/d/msgid/bitcoindev/CABaSBaxDjj6ySBx4v%2Brmpfrw4pE9b%3DJZJPzPQj_Z=
UiBg1HGFyA%40mail.gmail.com</a>.<br />

--0000000000007be8ff0610f8dc6d--