FEP-888d: Using w3id.org/fep as a namespace for extension terms and for FEP documents

I posted an issue here:

I’ll repeat the content verbatim:

I have very inconsistent support for getting context documents for FEPs. I get about 50% or more failures from the platform, with slow responses. I attached the output from the ab program to show the low reliability.

The status page shows 66% uptime:

https://status.codeberg.eu/status/codeberg

…and the main page for codeberg pages has a banner saying not to use it for production sites:

https://codeberg.page

Since most FEPs use the fediverse/fep: Fediverse Enhancement Proposals - Codeberg.org PURL namespace from FEP 888d, it should be possible to deploy the files to another static hosting service without changing clients; just change the redirect at w3id.

There are other static site hosting systems, like archive.org’s S3 service:

https://archive.org/developers/ias3.html

Also, companies like Fastly have been supportive of the Fediverse, and might be willing to give credits for static site hosting.

https://www.fastly.com/fast-forward