Repository navigation
🐞🔧:point the Discord invites at live ones - #886
Merged
Merged
Conversation
All four invites in SUPPORT.md had expired. Discord answers `Unknown Invite` for every one, so the document sending people to the preferred support venue sent them nowhere. The replacements resolve to #off-topic, #support and #general in the OpenINF Community server, checked against Discord's API. Both `#support` labels now name the same invite. They were two distinct codes for one channel, which is how one of them went stale unnoticed. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
DerekNonGeneric
added a commit
that referenced
this pull request
Sep 6, 2026
Link rot has reached this repository twice now that anyone noticed: the Discord invites in #886, and every image at the top of the README, which had been a broken-image icon for long enough that nobody was seeing it any more. Nothing here looks for it. remark-validate-links reads links within the project and stops at its edge. Weekly rather than on every pull request, and outside verify/ for the reason `verify.pullRequest` is: it reaches the network, and a host that is slow or rate-limiting has nothing to do with the change being reviewed. It opens an issue rather than a pull request, because where a rotted link should point instead is a decision, and often the answer is to delete the sentence around it. What it will not do is cry wolf, which is the only way a check like this survives. A 404 is the only status read as gone; a rate limit, a login wall or a bad afternoon is reported separately as a question that could not be answered. GitHub is a special case both ways: it answers 404 for any page it will not show an anonymous client -- the stargazer list of nodejs/node is a 404 from here -- so a 404 there is settled against the API instead, and a repository that is merely private is not called deleted unless a token can tell the difference. The question the API is asked is what has become of a repository, not merely whether it is there, because visibility decides what a 404 means. An earlier draft exempted raw.githubusercontent.com from asking at all, on the belief it has no login wall. It has: a raw path under a private repository is a 404 to anybody not signed in, exactly as a deleted one is, and the check called the first gone. Now `private` is a verdict of its own, `public` plus a 404 means the file or ref really has gone, and only `gone` condemns the repository. Run against this branch it finds seven dead links and no false ones. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
DerekNonGeneric
added a commit
that referenced
this pull request
Sep 6, 2026
Link rot has reached this repository twice now that anyone noticed: the Discord invites in #886, and every image at the top of the README, which had been a broken-image icon for long enough that nobody was seeing it any more. Nothing here looks for it. remark-validate-links reads links within the project and stops at its edge. Weekly rather than on every pull request, and outside verify/ for the reason `verify.pullRequest` is: it reaches the network, and a host that is slow or rate-limiting has nothing to do with the change being reviewed. It opens an issue rather than a pull request, because where a rotted link should point instead is a decision, and often the answer is to delete the sentence around it. What it will not do is cry wolf, which is the only way a check like this survives. A 404 is the only status read as gone; a rate limit, a login wall or a bad afternoon is reported separately as a question that could not be answered. GitHub is a special case both ways: it answers 404 for any page it will not show an anonymous client -- the stargazer list of nodejs/node is a 404 from here -- so a 404 there is settled against the API instead, and a repository that is merely private is not called deleted unless a token can tell the difference. What the check answers is whether a reader can follow a link, which is the only question its own repository can settle. So a 404 stands unless GitHub says the repository is public, in which case the page is probably one it shows only to somebody signed in. Nothing claims a repository was deleted: a 404 from the API is equally what a private repository returns to a caller that cannot see it, and the token a workflow is handed reaches only the repository it runs in. A HEAD is never allowed to condemn a link either. Some hosts answer it from a route table and the GET from the content, so every unsuccessful HEAD is retried before anything is concluded. Reading the links out of prose moved into a module of its own with tests, because a bracket is harder than it looks: `…/Function_(maths)` is a real address and `[F](…/Function_(maths))` ends with one bracket that is not. Counting settles it, and seven cases hold it there. Run against this branch it finds seven dead links and no false ones. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
DerekNonGeneric
added a commit
that referenced
this pull request
Sep 6, 2026
Link rot has reached this repository twice now that anyone noticed: the Discord invites in #886, and every image at the top of the README, which had been a broken-image icon for long enough that nobody was seeing it any more. Nothing here looks for it. remark-validate-links reads links within the project and stops at its edge. Weekly rather than on every pull request, and outside verify/ for the reason `verify.pullRequest` is: it reaches the network, and a host that is slow or rate-limiting has nothing to do with the change being reviewed. It opens an issue rather than a pull request, because where a rotted link should point instead is a decision, and often the answer is to delete the sentence around it. What it will not do is cry wolf, which is the only way a check like this survives. A 404 is the only status read as gone; a rate limit, a login wall or a bad afternoon is reported separately as a question that could not be answered. GitHub is a special case both ways: it answers 404 for any page it will not show an anonymous client -- the stargazer list of nodejs/node is a 404 from here -- so a 404 there is settled against the API instead, and a repository that is merely private is not called deleted unless a token can tell the difference. What the check answers is whether a reader can follow a link, which is the only question its own repository can settle. A 404 stands, with two exceptions and no others: the page is one of the two GitHub hides from anonymous visitors -- the stargazer and watcher lists -- and the repository is provably public. Being public is not on its own an excuse; a page that is merely absent from a public repository is still a page a reader cannot open, and treating visibility as the verdict would have hidden exactly that. Which pages those are was checked rather than assumed. Against a public repository the root, network members, contributor graphs, pulse, forks, activity, branches, tags, issues and pull requests all answer 200, and an address that does not exist answers 404 as it should. Nothing claims a repository was deleted: a 404 from the API is equally what a private repository returns to a caller that cannot see it, and the token a workflow is handed reaches only the repository it runs in. Nor is an API that declines to answer read as a no -- rate limited or unwell, it returns neither yes nor no, and turning somebody else's bad afternoon into a broken-link report is how a check earns its mute. A HEAD is never allowed to condemn a link either. Some hosts answer it from a route table and the GET from the content, so every unsuccessful HEAD is retried before anything is concluded. Reading the links out of prose moved into a module of its own with tests, because a bracket is harder than it looks: `…/Function_(maths)` is a real address and `[F](…/Function_(maths))` ends with one bracket that is not. Counting settles it, and seven cases hold it there. Run against this branch it finds seven dead links and no false ones. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
DerekNonGeneric
added a commit
that referenced
this pull request
Sep 6, 2026
Link rot has reached this repository twice now that anyone noticed: the Discord invites in #886, and every image at the top of the README, which had been a broken-image icon for long enough that nobody was seeing it any more. Nothing here looks for it. remark-validate-links reads links within the project and stops at its edge. Weekly rather than on every pull request, and outside verify/ for the reason `verify.pullRequest` is: it reaches the network, and a host that is slow or rate-limiting has nothing to do with the change being reviewed. It opens an issue rather than a pull request, because where a rotted link should point instead is a decision, and often the answer is to delete the sentence around it. What it will not do is cry wolf, which is the only way a check like this survives. A 404 is the only status read as gone; a rate limit, a login wall or a bad afternoon is reported separately as a question that could not be answered. GitHub is a special case both ways: it answers 404 for any page it will not show an anonymous client -- the stargazer list of nodejs/node is a 404 from here -- so a 404 there is settled against the API instead, and a repository that is merely private is not called deleted unless a token can tell the difference. What the check answers is whether a reader can follow a link, which is the only question its own repository can settle. A 404 stands, with two exceptions and no others: the page is one of the two GitHub hides from anonymous visitors -- the stargazer and watcher lists -- and the repository is provably public. Being public is not on its own an excuse; a page that is merely absent from a public repository is still a page a reader cannot open, and treating visibility as the verdict would have hidden exactly that. Which pages those are was checked rather than assumed. Against a public repository the root, network members, contributor graphs, pulse, forks, activity, branches, tags, issues and pull requests all answer 200, and an address that does not exist answers 404 as it should. Nothing claims a repository was deleted: a 404 from the API is equally what a private repository returns to a caller that cannot see it, and the token a workflow is handed reaches only the repository it runs in. Nor is an API that declines to answer read as a no -- rate limited or unwell, it returns neither yes nor no, and turning somebody else's bad afternoon into a broken-link report is how a check earns its mute. A HEAD is never allowed to condemn a link either. Some hosts answer it from a route table and the GET from the content, so every unsuccessful HEAD is retried before anything is concluded. Reading the links out of prose moved into a module of its own with tests, because a bracket is harder than it looks: `…/Function_(maths)` is a real address and `[F](…/Function_(maths))` ends with one bracket that is not. Counting settles it, and seven cases hold it there. Run against this branch it finds seven dead links and no false ones. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
DerekNonGeneric
added a commit
that referenced
this pull request
Sep 7, 2026
Link rot has reached this repository twice now that anyone noticed: the Discord invites in #886, and every image at the top of the README, which had been a broken-image icon for long enough that nobody was seeing it any more. Nothing here looks for it. remark-validate-links reads links within the project and stops at its edge. Weekly rather than on every pull request, and outside verify/ for the reason `verify.pullRequest` is: it reaches the network, and a host that is slow or rate-limiting has nothing to do with the change being reviewed. It opens an issue rather than a pull request, because where a rotted link should point instead is a decision, and often the answer is to delete the sentence around it. What it will not do is cry wolf, which is the only way a check like this survives. A 404 is the only status read as gone; a rate limit, a login wall or a bad afternoon is reported separately as a question that could not be answered. GitHub is a special case both ways: it answers 404 for any page it will not show an anonymous client -- the stargazer list of nodejs/node is a 404 from here -- so a 404 there is settled against the API instead, and a repository that is merely private is not called deleted unless a token can tell the difference. What the check answers is whether a reader can follow a link, which is the only question its own repository can settle. A 404 stands, with two exceptions and no others: the page is one of the two GitHub hides from anonymous visitors -- the stargazer and watcher lists -- and the repository is provably public. Being public is not on its own an excuse; a page that is merely absent from a public repository is still a page a reader cannot open, and treating visibility as the verdict would have hidden exactly that. Which pages those are was checked rather than assumed. Against a public repository the root, network members, contributor graphs, pulse, forks, activity, branches, tags, issues and pull requests all answer 200, and an address that does not exist answers 404 as it should. Nothing claims a repository was deleted: a 404 from the API is equally what a private repository returns to a caller that cannot see it, and the token a workflow is handed reaches only the repository it runs in. Nor is an API that declines to answer read as a no -- rate limited or unwell, it returns neither yes nor no, and turning somebody else's bad afternoon into a broken-link report is how a check earns its mute. A HEAD is never allowed to condemn a link either. Some hosts answer it from a route table and the GET from the content, so every unsuccessful HEAD is retried before anything is concluded. Reading the links out of prose moved into a module of its own with tests, because a bracket is harder than it looks: `…/Function_(maths)` is a real address and `[F](…/Function_(maths))` ends with one bracket that is not. Counting settles it, and seven cases hold it there. Run against this branch it finds seven dead links and no false ones. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
openinf-commit-queue Bot
pushed a commit
that referenced
this pull request
Sep 7, 2026
🏗️✨:watch the prose for links that have rotted Link rot has reached this repository twice now that anyone noticed: the Discord invites in #886, and every image at the top of the README, which had been a broken-image icon for long enough that nobody was seeing it any more. Nothing here looks for it. remark-validate-links reads links within the project and stops at its edge. Weekly rather than on every pull request, and outside verify/ for the reason `verify.pullRequest` is: it reaches the network, and a host that is slow or rate-limiting has nothing to do with the change being reviewed. It opens an issue rather than a pull request, because where a rotted link should point instead is a decision, and often the answer is to delete the sentence around it. What it will not do is cry wolf, which is the only way a check like this survives. A 404 is the only status read as gone; a rate limit, a login wall or a bad afternoon is reported separately as a question that could not be answered. GitHub is a special case both ways: it answers 404 for any page it will not show an anonymous client -- the stargazer list of nodejs/node is a 404 from here -- so a 404 there is settled against the API instead, and a repository that is merely private is not called deleted unless a token can tell the difference. What the check answers is whether a reader can follow a link, which is the only question its own repository can settle. A 404 stands, with two exceptions and no others: the page is one of the two GitHub hides from anonymous visitors -- the stargazer and watcher lists -- and the repository is provably public. Being public is not on its own an excuse; a page that is merely absent from a public repository is still a page a reader cannot open, and treating visibility as the verdict would have hidden exactly that. Which pages those are was checked rather than assumed. Against a public repository the root, network members, contributor graphs, pulse, forks, activity, branches, tags, issues and pull requests all answer 200, and an address that does not exist answers 404 as it should. Nothing claims a repository was deleted: a 404 from the API is equally what a private repository returns to a caller that cannot see it, and the token a workflow is handed reaches only the repository it runs in. Nor is an API that declines to answer read as a no -- rate limited or unwell, it returns neither yes nor no, and turning somebody else's bad afternoon into a broken-link report is how a check earns its mute. A HEAD is never allowed to condemn a link either. Some hosts answer it from a route table and the GET from the content, so every unsuccessful HEAD is retried before anything is concluded. Reading the links out of prose moved into a module of its own with tests, because a bracket is harder than it looks: `…/Function_(maths)` is a real address and `[F](…/Function_(maths))` ends with one bracket that is not. Counting settles it, and seven cases hold it there. Run against this branch it finds seven dead links and no false ones. 🏗️🔧:let the link check actually run This never ran. The workflow said the task "reads only what node ships with, so there is nothing to install", and it does not: check-links imports `glob` from build/utils, which imports @isaacs/catcher and @yarnpkg/shell. With no install step the job died at that import with ERR_MODULE_NOT_FOUND. Worse than a red X, because of what the exit code then meant. node exits 1 on an uncaught exception and `DEAD` is also 1, so the failure read as a dead link, and the next step filed the weekly issue with an empty body. A check that cries wolf is the one thing this was written not to be. Two changes, either of which would have caught it. The dependencies are installed, the way every other workflow here installs them. And the exit code is now believed only when it is one of the four the task can produce and the report is not empty -- the task prints its summary line before any finding, so an empty report means it did not get that far. Anything else fails the job loudly and files nothing. check-links also gains the `matched` guard af2e821 gave the verify tasks while this branch was open. It discovers its own files, so a glob that stopped matching would have reported zero links and nothing wrong with any of them. Run end to end here for the first time: 71 links, exit 3, a 953-byte report. It found two that are gone -- both anchors on OpenINF/wg-a-team, from doc/adr/0004 -- and correctly held back the rate-limited and login-walled ones as unchecked rather than dead, including the stargazers page the GitHub special case is there for. Those two dead links are left for the issue this will file. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5 PR-URL: #899
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every Discord invite in
SUPPORT.mdhad expired. Checked against Discord's APIrather than by clicking:
So the document that names Discord as the preferred venue, over a Matrix room
it describes as mostly defunct, was sending everyone nowhere at all.
The replacements resolve to the right channels in the OpenINF Community server:
The two support labels
[`#support` channel]and[support-channel-discord]were two differentinvite codes for the same channel, and both are used in the same paragraph.
They now name the same invite. Two codes for one destination is how one of them
went stale without anyone noticing.
Why this repository
SUPPORT.mdhere is the source.openinf.github.iogeneratescollections/_docs/support.mdfrom it at build time viacompile.siteifyHealthFiles, and its own ignore file says fixes applied thereare overwritten on the next build. So this is the only place the change holds.
The same three invites are being fixed on the OpenINF home page separately, in
OpenINF/openinf.github.io#1833, where they are hardcoded rather than generated.
Checks
Every reference-style link in the file still resolves to a definition. I did
not run
pnpm testfor this one: the change is four URLs inside a linkdefinition block, and the toolchain install is a large cost for that. Say the
word if you would rather it ran.