Skip to content

Fix three dead links reported by the weekly link check - #3748

Open
SurefireStudios wants to merge 1 commit into
github:mainfrom
SurefireStudios:fix-dead-links-weekly-check
Open

SurefireStudios wants to merge 1 commit into
github:mainfrom
SurefireStudios:fix-dead-links-weekly-check

Conversation

@SurefireStudios

@SurefireStudios SurefireStudios commented Sep 14, 2026

Copy link
Copy Markdown
  • Have you followed the contributing guidelines?
  • Have you explained what your changes do, and why they add value to the Guides?

What this does

The Weekly External Link Check has failed on every scheduled run since at least 13 July — ten in a row, most recently 34821005741.

This fixes the three URLs in that report that are genuinely dead.

Per docs/translations.md, each URL is updated in every language and only the URL changes — no translated prose is touched.

Article Link Status Fix
finding-users @jhamrick, "How I learned to Stop Worrying and Love PyCon" 404 Internet Archive, snapshot 2026-08-04
legal @bcantrill, "Broadening Node.js Contributions" 404 Internet Archive of the joyent.com original, snapshot 2022-05-28
how-to-contribute (ko, zh-hant only) Steinmacher et al., SANER 2016 404 ime.usp.br copy, matching the other 28 files

jesshamrick.com no longer serves the post under any URL form I could find, and the site root itself returns 403.

"Broadening Node.js Contributions" is gone from tritondatacenter.com, from the tritoncloud.io it redirects to, and from joyent.com where it was originally published, so I pointed at the archive of the joyent.com original.

The SANER 2016 paper was already fixed in English and 27 translations; ko and zh-hant still had the dead igor.pro.br URL, so this brings all 30 into agreement.

Archiving dead citations follows what the guides already do in roughly 220 article files.

What I deliberately left alone

openinventionnetwork.com returns 200 for me with both a browser and a plain user agent, so that failure looks transient.

stackoverflow.com, gitlab.com/explore/projects/trending and governingopen.com all return 403 to automated clients while working in a browser — those are url_ignores candidates for script/html-proofer rather than content fixes, and I left them out since that changes tooling. Happy to open a separate PR if you want them.

How I checked

Each URL was requested directly with both user agents, following redirects, recording the final status and effective URL rather than trusting the CI log; the replacement archive URLs return 200.

With URLs masked out, all 58 changed lines are byte-identical to their originals, confirming no translated text was altered.

The Weekly External Link Check has failed on every scheduled run since at
least 13 July. Three of the URLs it reports now return 404 to any client.
Following docs/translations.md, each is fixed across every translation and
only the URL is changed, so no translated prose is touched.

- finding-users: @jhamrick, "How I learned to Stop Worrying and Love PyCon".
  jesshamrick.com no longer serves the post under any URL form, and the site
  root returns 403. Replaced with the Internet Archive snapshot of
  2026-08-04, matching how the guides already cite ~220 other dead sources.

- legal: @bcantrill, "Broadening Node.js Contributions". The post is gone
  from tritondatacenter.com, from tritoncloud.io that it now redirects to,
  and from joyent.com where it was originally published. Replaced with the
  Internet Archive snapshot of the joyent.com original from 2022-05-28.

- how-to-contribute (ko, zh-hant): the Steinmacher SANER 2016 paper at
  igor.pro.br is a 404. The English article and the other 27 translations
  already point at the ime.usp.br copy; these two were missed. Updated to
  match, so all 30 now agree.

Not changed: openinventionnetwork.com is also reported by the weekly run,
but it returns 200 with both a browser and a plain user agent, so that
failure looks transient rather than real. The remaining reported URLs
(stackoverflow.com, gitlab.com/explore, governingopen.com) answer 403 to
automated clients while working in a browser; those are ignore-list
candidates rather than content fixes, so they are left alone here.
Copilot AI balanced review requested due to automatic review settings September 14, 2026 18:15
@SurefireStudios
SurefireStudios requested a review from a team as a code owner September 14, 2026 18:15

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants