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.
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)
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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The FLOSS/fund validator refused the manifest:
I had read the rule as "point every URL at the domain that owns the project". It is the opposite. A
wellKnownmust sit on the same hostname as theurlit 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
repositoryUrlvalues are codeberg.org, which is where this manifest is served from, so their provenance is implicit and thosewellKnownfields 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