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.
I fully agree. And you nailed it. This was exactly what I try to explain what is wrong with ActivityPub FEPs.
Thank you, we do indeed publish those schemas, these are coming from the code. So our documentation build is also relying on our code to expose these schemas, and that’s also why I can guarantee it’s always up to date.
For example we have ap issues with lemmy, lemmy doesn’t support multiple attachments. We use attachments for both links (url, other than image links) as well as images themselves can be an attachment.
But again AP fails, and lemmy only shows the picture.