A wellKnown belongs on the host of the URL it vouches for #85

Merged
extant2000git merged 1 commits from fix/funding-wellknown-hosts into main 2026-10-15 22:37:44 +00:00
Owner

The FLOSS/fund validator refused the manifest:

projects[flamenet-messenger].repositoryUrl.url and projects[flamenet-messenger].repositoryUrl.wellKnown hostnames do not match

I had read the rule as "point every URL at the domain that owns the project". It is the opposite. A wellKnown must sit on the same hostname as the url it accompanies, because it is that host attesting to the manifest, and it is only needed when the hostname differs from the one serving the manifest.

Both repositoryUrl values are codeberg.org, which is where this manifest is served from, so their provenance is implicit and those wellKnown fields are removed. The three that remain sit on flamenetmessenger.com, which does differ from the manifest host, and that path returns 200 with the manifest URL.

Both rules checked locally rather than by resubmitting: the hostname rule and the v1.1.0 schema fetched from fundingjson.org.

🤖 Generated with Claude Code

The FLOSS/fund validator refused the manifest: > projects[flamenet-messenger].repositoryUrl.url and projects[flamenet-messenger].repositoryUrl.wellKnown hostnames do not match I had read the rule as "point every URL at the domain that owns the project". It is the opposite. A `wellKnown` must sit on the **same** hostname as the `url` it accompanies, because it is that host attesting to the manifest, and it is only needed when the hostname differs from the one serving the manifest. Both `repositoryUrl` values are codeberg.org, which is where this manifest is served from, so their provenance is implicit and those `wellKnown` fields are removed. The three that remain sit on flamenetmessenger.com, which does differ from the manifest host, and that path returns 200 with the manifest URL. Both rules checked locally rather than by resubmitting: the hostname rule and the v1.1.0 schema fetched from fundingjson.org. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
extant2000git added 1 commit 2026-10-15 22:35:54 +00:00
A wellKnown belongs on the host of the URL it vouches for
ci / spec-counts (pull_request) Successful in 27s
ci / analysis (pull_request) Successful in 1m28s
ci / ratchet (pull_request) Successful in 5s
ci / secret-sweep (pull_request) Successful in 6s
ci / conformance (pull_request) Successful in 12s
ci / complete (pull_request) Successful in 3s
ci / vault (pull_request) Successful in 4s
ci / doc-references (pull_request) Successful in 3s
ci / client (pull_request) Successful in 28s
262b794327
The FLOSS/fund validator refused the manifest: "projects[flamenet-messenger].
repositoryUrl.url and projects[flamenet-messenger].repositoryUrl.wellKnown
hostnames do not match."

I had read the rule as "point every URL at the domain that owns the project".
It is the opposite. A wellKnown must sit on the SAME hostname as the url it
accompanies, because it is that host attesting to the manifest, and it is only
needed at all when the hostname differs from the one serving the manifest.

Both repositoryUrl values are codeberg.org, which is where this manifest is
served from, so their provenance is implicit and the wellKnown fields are gone.
The three that remain are on flamenetmessenger.com, which does differ from the
manifest host, and that path answers 200 with the manifest URL.

Checked both rules locally rather than by resubmitting.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
extant2000git merged commit de7442cf2b into main 2026-10-15 22:37:44 +00:00
Sign in to join this conversation.