Today @mkljczk 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
https://codeberg.org/fediverse-pl/maep/issues/1
#fedidev #fediverse #MAEPs
Discussion
Loading...
To help highlight the issues that this proposal seeks to mitigate, @mkljczk has made a very extensive table of implementers of the Mastodon API who have already extended it in various ways:
https://codeberg.org/mkljczk/nicolium/wiki/List-of-Mastodon-API-server-implementations
@mro how many client apps support seppo with a nice well thought out accessible UI? We are not talking about one product at all here. We are talking about the most used client API in the fediverse that's used in practice by hundreds of compleatly different projects
This is an area I have an unreasonable amount of conversations about over the past years and this proposal seems like a very reasonable shorter term solution to some of the issues we (fediverse meta discussions) have all been talking about lately.
This is slightly tangential to the work on the ActivityPub C2S API situation being spearheaded by lately by @django