wakest ⁂ @liaizon@social.wake.st
Public

Today @mkljczknicole mikołajczyk introduced a proposal for MAEPs (Mastodon API Enhancement Proposals) which would be similar to the FEP process but for converging on API schema for servers that are not Mastodon but who are using the Mastodon client API
codeberg.org/fediverse-pl/maep

Summary card of an issue titled "Why MAEPs? What should they look like?" in repository fediverse-pl/maep

Why MAEPs? What should they look like?

# Motivation The Mastodon API has become the de facto standard API for Fediverse microblogging apps[^1], with [more than 20 reimplementations](https://codeberg.org/mkljczk/nicolium/wiki/List-of-Mastodon-API-server-implementations). They often implement a subset of the API, but they also extend i...

codeberg.org · Codeberg.org

0
1
1

If you have a fediverse account, you can quote this note from your own instance. Search https://social.wake.st/users/liaizon/statuses/116098978692376296 on your instance and quote it. (Note that quoting is not supported in Mastodon.)

Emelia 👸🏻 @thisismissem@hachyderm.io
Public

RE: social.wake.st/@liaizon/116098

This is like saying you're doing "S3 Extension Proposals", because "multiple projects implemented S3-compatible (enough) APIs and Clients"

The only one that defines S3's API is AWS.

It's not a standard no matter how many projects implement it.

The Mastodon API is defined by Mastodon only. It's not a standard no matter how much people want to treat it as a standard. Use C2S / ActivityPub API.

If you want to advance the Fediverse, there's plenty of taskforces at Social Web CG that need help writing FEPs and standards documents. It's not as hard as you might think, just time consuming.

0
0
0