Upgrade MastoAPI baseline (compatible Mastodon version) #1027

New issue

Closed

opened 2025-11-30 00:46:04 +00:00 by Oneric · 1 comment

Oneric commented

2025-11-30 00:46:04 +00:00

Owner

Currently we advertise ourself as being compatible with Mastodon 2.7.2 from February 2019.
Since then there have been two major and many minor releases removing and adding new API endpoints and parameters; as of writing the current release is Mastodon 4.5.2.

We have all API endpoints and parameters from 2.7.2, plus various random bits from newer versions we since added, often for compat with existing clients. Understandably clients often do not consider the API from almost 7 years ago when implementing their side of the interaction and so unless a client is written specifically with Akkoma in mind we are more and more likely to run into interop issues. Even Husky had some issues recently (since we didn't support the newer, Mastodon-compatible parameter name for a functionality formerly provided as an *oma extension).

Thus it would be good to upgrade our baseline compatibility, at least to 4.0. Unfortunately the relevant bits don’t seem to always be easy to get out of Mastodon’s changelog and someone will probably have to go over the current web API docs at joinmastodon.org and note down all additions since 2.7.2 and the version they were introduced in.
Once we have this list the missing bits can be implemented bit by bit.

Other than the quote mess already described in #1009 there hopefully shouldn't be any major issues. And stuff we just don’t want to support we can just stub out the response, but that’s probably only a tiny minority.

Currently we advertise ourself as being compatible with Mastodon `2.7.2` from February 2019. Since then there have been two major and many minor releases removing and adding new API endpoints and parameters; as of writing the current release is Mastodon `4.5.2`. We have all API endpoints and parameters from 2.7.2, plus various random bits from newer versions we since added, often for compat with existing clients. Understandably clients often do not consider the API from almost 7 years ago when implementing their side of the interaction and so unless a client is written specifically with Akkoma in mind we are more and more likely to run into interop issues. Even Husky had some issues recently *(since we didn't support the newer, Mastodon-compatible parameter name for a functionality formerly provided as an \*oma extension)*. Thus it would be good to upgrade our baseline compatibility, at least to 4.0. Unfortunately the relevant bits don’t seem to always be easy to get out of Mastodon’s changelog and someone will probably have to go over the current web API docs at joinmastodon.org and note down all additions since 2.7.2 and the version they were introduced in. Once we have this list the missing bits can be implemented bit by bit. Other than the quote mess already described in #1009 there hopefully shouldn't be any major issues. And stuff we just don’t want to support we can just stub out the response, but that’s probably only a tiny minority.