Moving FEP context documents off Codeberg Pages
-
I started a ticket on the FEP repository about the poor performance of Codeberg Pages.
Move context documents off Codeberg Pages
fep - Fediverse Enhancement Proposals
Codeberg.org (codeberg.org)
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.
Move context documents off Codeberg Pages
fep - Fediverse Enhancement Proposals
Codeberg.org (codeberg.org)
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)
trwnh@mastodon.social Ah, I misunderstood.
Let me know if I can help out. I can't participate in the FEPs tracking topic because it isn't federated.
-
trwnh@mastodon.social Ah, I misunderstood.
Let me know if I can help out. I can't participate in the FEPs tracking topic because it isn't federated.
@evan probably the first step would be to propose a FEP project-wide adoption of an alternate file host other than Codeberg? once such a thing is adopted, the w3id config can be edited.
-
@evan probably the first step would be to propose a FEP project-wide adoption of an alternate file host other than Codeberg? once such a thing is adopted, the w3id config can be edited.
trwnh@mastodon.social said in Moving FEP context documents off Codeberg Pages:
> evan probably the first step would be to propose a FEP project-wide adoption of an alternate file host other than Codeberg? once such a thing is adopted, the w3id config can be edited.That's going to take a long time. If you want to have 888d work, you need to be more proactive.
-
trwnh@mastodon.social said in Moving FEP context documents off Codeberg Pages:
> evan probably the first step would be to propose a FEP project-wide adoption of an alternate file host other than Codeberg? once such a thing is adopted, the w3id config can be edited.That's going to take a long time. If you want to have 888d work, you need to be more proactive.
@evan I don't think it's going to take a long time. If you have a file host you'd like to propose that we can mirror the Codeberg fediverse/fep repo to, then by all means, propose one.
In any case, the lack of availability of a response over HTTPS should not be taken to mean that a context "doesn't work". Newer W3C specs recommend preloading contexts with known content+hashes ahead-of-time: https://www.w3.org/TR/vc-data-model-2.0/#base-context
> Implementations MUST treat the base context value [...] as already retrieved
