impersonation: switch Twitter for X

_config.yml

@@ -33,7 +33,7 @@ exclude:
   - README.md
   - CONTRIBUTING.md
   - CNAME
-  - vendor  # Travis CI creates a vendor/ dir with files we shouldn't render
+  - vendor  # CI creates a vendor/ dir with files we shouldn't render
   - contrib
   - Makefile
 

_includes/footer.html

@@ -1,6 +1,6 @@
 <div>
     <span>
-        <a href="https://twitter.com/bitcoincoreorg" target="_blank" class=""><i class="fa fa-fw fa-twitter"></i>Twitter</a><br />
+        <a href="https://x.com/bitcoincoreorg" target="_blank" class=""><i class="fa fa-fw fa-twitter"></i>Twitter</a><br />
         <a href="/en/legal/">Legal</a> | <a href="/en/legal/privacy">Privacy Policy</a> | <a href="/{{ page.lang }}/rss/">RSS <img src="/assets/images/rss-24x24.png" alt="rss feeds" width="14" height="14"></a>
     </span>
 </div>

_includes/references.md

@@ -116,7 +116,7 @@
 [BIP173]: https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki
 [BIP174]: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki
 
-[@bitcoincoreorg]: https://twitter.com/bitcoincoreorg
+[@bitcoincoreorg]: https://x.com/bitcoincoreorg
 [#bitcoin-core-dev]: https://web.libera.chat/#bitcoin-core-dev
 [#bitcoin-core-builds]: https://web.libera.chat/#bitcoin-core-builds
 [#bitcoin-core-gui]: https://web.libera.chat/#bitcoin-core-gui

_posts/en/pages/2016-01-15-lifecycle.md

@@ -81,4 +81,4 @@ Parts of Bitcoin, most notably the consensus rules, don't work that way.  In ord
 For this reason, Bitcoin Core deviates from SemVer for changes to consensus rules and other updates where network-wide adoption is necessary or desirable.  Bitcoin Core releases these changes as maintenance releases (`x.y`) instead of as major releases (`x.0`); this minimizes the size of the patch in order to make it easy for as many people as possible to inspect it, test it, and deploy it.  It also makes it possible to backport the same patch to multiple previous major releases, further increasing the number of users who can easily upgrade, although there are not always enough volunteers to manage this.
 
 [SemVer]: https://semver.org/
-[bitcoin-transifex-link]: https://www.transifex.com/bitcoin/bitcoin/
+[bitcoin-transifex-link]: https://explore.transifex.com/bitcoin/bitcoin/

_posts/en/pages/2016-03-12-contact.md

@@ -16,7 +16,7 @@ version: 2
 <hr>
 </center>
 
-<i class="fa fa-fw fa-twitter"></i> <span style="color:black">Twitter: <a href="https://twitter.com/bitcoincoreorg/">@bitcoincoreorg</a></span>
+<i class="fa fa-fw fa-twitter"></i> <span style="color:black">Twitter: <a href="https://x.com/bitcoincoreorg/">@bitcoincoreorg</a></span>
 
 You can report bugs in our software using the <i class="fa fa-fw fa-github"></i> [issue tracker][issues].
 

_posts/en/pages/2017-01-01-twitter-impersonation.md

@@ -7,20 +7,20 @@ layout: page
 lang: en
 version: 1
 ---
-We are aware of several accounts on Twitter that violate [Twitter's
+We are aware of several accounts on X (previously Twitter) that violate [X's
 Impersonation Policy][] by pretending to be the Bitcoin Core project or
 well-known individuals associated with Bitcoin Core.  These accounts
 have been spreading false and misleading information about Bitcoin Core
 and its contributors.
 
-If you see one of these accounts, you may [report it to Twitter][].  If
-you are reporting an issue about the Bitcoin Core project and Twitter
+If you see one of these accounts, you may [report it to X][].  If
+you are reporting an issue about the Bitcoin Core project and X
 asks that you enter the project's official email address, please use:
 contact<span style="display:none"></span>@bitcoincore.org
 
-This appears to be an unfortunately common issue on Twitter that affects
+This appears to be an unfortunately common issue on X that affects
 many other projects and individuals as well, so we urge you to carefully
-evaluate any posts you see on Twitter---and elsewhere---to determine
+evaluate any posts you see on X---and elsewhere---to determine
 whether or not they truly came from the indicated sender.
 
 It is especially important to be careful about posts that recommend you
@@ -38,17 +38,17 @@ and aren't sure whether or not it is legitimate, you can safely shutdown
 your Bitcoin Core program to eliminate any immediate problems and give
 yourself time to investigate.
 
-Although Bitcoin Core does have an official Twitter account,
+Although Bitcoin Core does have an official X account,
 [@bitcoincoreorg][], any important announcements about the project will
 also sent to our low-traffic [announcements mailing list][] or posted on
 the [front page of this website][] (which also has an [RSS feed][]).  If
 you know how to use PGP security software, subscribing to the mailing
 list is particularly recommended as all announcements will be
 cryptographically signed by a developer.
 
-[Twitter's Impersonation Policy]: https://support.twitter.com/articles/18366#
-[report it to Twitter]: https://support.twitter.com/forms/impersonation
-[@bitcoincoreorg]: https://twitter.com/bitcoincoreorg
+[X's Impersonation Policy]: https://help.x.com/en/rules-and-policies/authenticity
+[report it to X]: https://help.x.com/en/forms/authenticity/impersonation
+[@bitcoincoreorg]: https://x.com/bitcoincoreorg
 [announcements mailing list]: /en/list/announcements/join/
 [front page of this website]: /
 [RSS feed]: /en/rss.xml

_posts/ja/pages/2016-03-12-contact.md

@@ -13,7 +13,7 @@ version: 2
 
 ソフトウェアのバグを報告する際は、<i class="fa fa-fw fa-github"></i> [issue tracker][issues] を使用してください。
 
-<i class="fa fa-fw fa-twitter"></i> Twitter: <a href="https://twitter.com/bitcoincoreorg/">@bitcoincoreorg</a>
+<i class="fa fa-fw fa-twitter"></i> Twitter: <a href="https://x.com/bitcoincoreorg/">@bitcoincoreorg</a>
 
 Bitcoin Coreの開発者は [IRC][#bitcoin-core-dev]にいます。
 

contrib/qa/test-binary-availability.sh

@@ -1,6 +1,6 @@
 #!/bin/bash 
 
-# Local builds and Travis CI builds of the BitcoinCore.org website do
+# Local builds and CI builds of the BitcoinCore.org website do
 # not include the /bin directory holding Bitcoin Core binaries, so this
 # test extracts the local URLs from the download page and checks that
 # they exist on the remote server.  Only the file's HTTP headers are