as discussed in https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171/38?u=trwnh onward, and as described in https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171/57?u=trwnh
Open considerations:
1. This PR copies `feps/fep-xxxx.md` to `fep/xxxx/fep-xxxx.md` for now. There is some consideration for naming it `index.md` instead, in order to ease with potential future static site generation via CI/CD. Imagine a CI/CD task that clones the repo and generates a proper site using `fep` as the content directory. (The idea is that this site may then be served to anyone requesting text/html representations of the `https://w3id.org/fep/xxxx` URI following the specifications laid out in FEP-9606.)
2. This PR does not yet delete any old paths. Everything in `feps/` has been edited to contain a Markdown link to the new location.
Rationale:
- We have encountered FEPs that wish to create their own assets, and the current structure is confusingly laid out. Asset colocation is widely considered a "best practice" for this sort of scenario. Particularly in cases where the rest of the repo's structure may potentially change in the future, asset colocation prevents any FEP-specific links from breaking because those links can be written relative to their FEP root.
- To ease PURL resolution, context documents can be considered sidecar assets to each FEP that defines extension terms. The mechanism for this is again described in FEP-9606. Redirection rules can be simplified to use less conditions, since the base folder remains the same.
Next steps:
- Edit the README.md to update the instructions for submitting a new FEP (pending open consideration 1)
- Set a timeline for when or if the old `feps/` directory should be removed (pending open consideration 2)
- Merge this PR
Co-authored-by: a <a@trwnh.com>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/109
Co-authored-by: a <trwnh@noreply.codeberg.org>
Co-committed-by: a <trwnh@noreply.codeberg.org>
This is an extensive update to FEP-fffd:
- Proxy links are now `Link`s in `url` with `"rel": "alternate"` or `"rel": "canonical"`. The new `@context` entries have been removed entirely.
- Protocols are determined by URI scheme and/or `mediaType`, not an explicit `protocol` URI.
- Added ATProto, DID, Secure Scuttlebutt, RSS, Atom, and ActivityPub to the list of well-known protocols.
- Specified that only bare NIP-19 identifiers can be used in Nostr URIs.
- Added a section to explain the merging "algorithm", mostly the situations in which merging breaks down and should be skipped.
- Removed references to Zot, since no bridging is needed for Zot.
- More clarity about which sections are normative.
- Added a reference to proxies for moved ActivityPub posts, which seems like an ideal use case not considered before.
Co-authored-by: Adam R. Nelson <adam@nels.onl>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/99
Co-authored-by: Adam Nelson <arnelson@noreply.codeberg.org>
Co-committed-by: Adam Nelson <arnelson@noreply.codeberg.org>
Proposal for FEP-fffd: Proxy Objects
This FEP proposes a way to identify ActivityPub objects that are proxies for objects from other protocols: for example, posts bridged from Nostr or Twitter, or posts syndicated across multiple protocols simultaneously.
Co-authored-by: Adam R. Nelson <adam@nels.onl>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/94
Co-authored-by: Adam Nelson <arnelson@noreply.codeberg.org>
Co-committed-by: Adam Nelson <arnelson@noreply.codeberg.org>
a
Adam Nelson