The FLOSS/fund directory listed both repository links as unverified: "The funding manifest has not provided proof via wellKnown that this link is associated with it."
Sharing codeberg.org with the manifest proves nothing, because anyone can serve a manifest from codeberg.org. The spec example is a file committed inside the repository it vouches for:
So .well-known/funding-manifest-urls holds the manifest URL, and each repositoryUrl.wellKnown points at that file in its own repository. The hostname still matches the url beside it, which is what the validator rejected on the first attempt.
flamenet-relay carries the same file for the flamenet-messenger project, in extant2000/flamenet-relay.
The FLOSS/fund directory listed both repository links as unverified: "The funding manifest has not provided proof via wellKnown that this link is associated with it."
Sharing codeberg.org with the manifest proves nothing, because anyone can serve a manifest from codeberg.org. The spec example is a file committed **inside the repository it vouches for**:
https://github.com/example/zombo-app/blob/main/.well-known/funding-manifest-urls
So `.well-known/funding-manifest-urls` holds the manifest URL, and each `repositoryUrl.wellKnown` points at that file in its own repository. The hostname still matches the `url` beside it, which is what the validator rejected on the first attempt.
flamenet-relay carries the same file for the flamenet-messenger project, in extant2000/flamenet-relay.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The directory listed both repository links as "Unverified URL: The funding
manifest has not provided proof via wellKnown that this link is associated with
it."
Sharing codeberg.org with the manifest proves nothing, because anyone can serve
a manifest from codeberg.org. The spec's own example is a file committed inside
the repository it vouches for:
https://github.com/example/zombo-app/blob/main/.well-known/funding-manifest-urls
So .well-known/funding-manifest-urls holds the manifest URL, and each
repositoryUrl.wellKnown points at that file's raw path in its own repository.
The hostname still matches the url beside it, which is what the validator
checked the first time round.
flamenet-relay needs the same file for the flamenet-messenger project, in its
own repository.
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 directory listed both repository links as unverified: "The funding manifest has not provided proof via wellKnown that this link is associated with it."
Sharing codeberg.org with the manifest proves nothing, because anyone can serve a manifest from codeberg.org. The spec example is a file committed inside the repository it vouches for:
So
.well-known/funding-manifest-urlsholds the manifest URL, and eachrepositoryUrl.wellKnownpoints at that file in its own repository. The hostname still matches theurlbeside it, which is what the validator rejected on the first attempt.flamenet-relay carries the same file for the flamenet-messenger project, in extant2000/flamenet-relay.
🤖 Generated with Claude Code