Fediverse Enhancement Proposals

A Fediverse Enhancement Proposal (FEP) is a document that provides information to the Fediverse community. The goal of a FEP is to improve interoperability and well-being of diverse services, applications and communities that form the Fediverse.

The FEP Process is an initiative of the SocialHub developer community, a liaison of the W3C Social Web Incubator Community Group.

Discovered this today. If you're on the developer side of things or are interested in how the Fediverse / ActivityPub is being built and enhanced, take a look at this codeberg repo.

fep

fep - Fediverse Enhancement Proposals

Codeberg.org (codeberg.org)

Thats super cool!

Indeed, this is where the majority of improvements to the Fediverse are shared for archival.

The very way Lemmy Piefed Mbin and NodeBB can communicate and synchronize communities is detailed in those FEPs. Check out FEP 1b12.

Hi Melroy from Mbin. It's true what you are saying Julian. These FEPs forms the basic of the fediverse.
But at the same time I hate those FEPs alot. I would rather see a more detailed and better described ActivityPub protocol v2.0 or 3.0. My point is that the current ActivityPub is way too vague.

And we need dozens of various FEPs to get the features we actually need and want to get the basis features of today. Currently it's hard to read, there is no single document. No single source of truth. All FEPs are actually optional to implement. And it's a mess.

Could you imagine if an internet standard like http or TCP was documented like this? It would never have worked.

I knew that there was some kind of unifying force in the Fediverse. Thanks for sharing it.

>Currently it's hard to read, there is no single document. No single source of truth.

We can make it happen.

I am currently working on this: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md. It's a guide for developers, but in the future it may be used as a base for a more formal specification.

Hmm, how do you reconcile the fact that not all FEPs are applicable to all application types?

For example soft deletion is preferable but not required...