There's now a proper rendered web interface for FEPs at `https://fediverse.codeberg.page/fep/fep/*/`, which is much nicer to read than the raw Markdown source on Codeberg.
-
There's now a proper rendered web interface for FEPs at
https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink,https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.
I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)
#fedidev #fep #fediverse #ActivityPub
-
There's now a proper rendered web interface for FEPs at
https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink,https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.
I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)
#fedidev #fep #fediverse #ActivityPub
@hongminhee Content Negotiation!
-
There's now a proper rendered web interface for FEPs at
https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink,https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.
I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)
#fedidev #fep #fediverse #ActivityPub
@hongminhee@hollo.social the w3id pages point to the rendered resource afaik?
The codeberg page is nicer, but the existing pages are okay too
-
@silverpill@mitra.social Ah, I see. In that case, it would be great if canonical permalinks could be decided for the FEP documents first!
-
R relay@relay.an.exchange shared this topic
-
@silverpill@mitra.social Ah, I see. In that case, it would be great if canonical permalinks could be decided for the FEP documents first!
@hongminhee @silverpill i'm not sure what the "canonical" identifier would be for a FEP; currently there is no canonical identifier. there is the codeberg repo and there is the w3id.org purl service from 888d and there is also the newer codeberg.page site
re: 888d itself the FEP is near finalization, pending some open questions about what finalization means https://socialhub.activitypub.rocks/t/fep-888d-using-w3id-org-fep-as-a-namespace-for-extension-terms-and-for-fep-documents/3098/55
the w3id.org htaccess could be updated to point at fediverse.codeberg.page if there are less issues with that, tho
