Moving FEP context documents off Codeberg Pages
-
I started a ticket on the FEP repository about the poor performance of Codeberg Pages.
https://codeberg.org/fediverse/fep/issues/670
I get about 50% failures when requesting JSON-LD docs from Codeberg Pages, with long delivery times:
https://codeberg.org/attachments/cb2513e6-8a6c-4d5c-bf5f-1654fdf83ba2
Codeberg has been a great supporter of the FEP process, and I don't want to throw them under the bus, but their landing page says not to use Codeberg Pages for production use:
The status page shows 66% uptime:
Codeberg Service Status
This is an overview of the Codeberg Infrastructure. Uptime stats are calculated over the past 24 hours only. The 14-days uptime of our primary instance is
(status.codeberg.eu)
Since most FEPs use the w3id.org/fep 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, built for the long term:
Also, companies like Fastly have been supportive of the Fediverse, and might be willing to give credits for static site hosting.
Fast Forward - how we're building the open internet
The internet is a pretty neat place. It’s where the world’s most creative minds gather to build things that benefit everyone. Open source, open standards, or just the open internet — with every contribution, you make the internet even better.
(www.fastly.com)
-
I started a ticket on the FEP repository about the poor performance of Codeberg Pages.
https://codeberg.org/fediverse/fep/issues/670
I get about 50% failures when requesting JSON-LD docs from Codeberg Pages, with long delivery times:
https://codeberg.org/attachments/cb2513e6-8a6c-4d5c-bf5f-1654fdf83ba2
Codeberg has been a great supporter of the FEP process, and I don't want to throw them under the bus, but their landing page says not to use Codeberg Pages for production use:
The status page shows 66% uptime:
Codeberg Service Status
This is an overview of the Codeberg Infrastructure. Uptime stats are calculated over the past 24 hours only. The 14-days uptime of our primary instance is
(status.codeberg.eu)
Since most FEPs use the w3id.org/fep 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, built for the long term:
Also, companies like Fastly have been supportive of the Fediverse, and might be willing to give credits for static site hosting.
Fast Forward - how we're building the open internet
The internet is a pretty neat place. It’s where the world’s most creative minds gather to build things that benefit everyone. Open source, open standards, or just the open internet — with every contribution, you make the internet even better.
(www.fastly.com)
@evan this would be a good idea! Just need to pick a place to push the data that's reliable and then update the w3id.org/fep PURL namespace.
-
@evan this would be a good idea! Just need to pick a place to push the data that's reliable and then update the w3id.org/fep PURL namespace.
@thisismissem @evan in theory anything that could serve a copy of the fep repo would work, since the conneg is handled at the w3id side via .htaccess rules. the problem is keeping it up-to-date and synced with the "canonical" repo on codeberg (or choosing a new "canonical", etc).
