manton
manton

Ricardo Mendes:

Sometimes I’m wondering, what would be the cost of stopping supporting the Mastodon API layer and instead work towards proper implementation of client to servers opening the route for a universal mobile app for #fedify based AP implementation.

The Mastodon API is a dead-end. It’s too specific to Mastodon. Client apps should be using either Micropub or ActivityPub client-to-server API, both W3C standards.

|
Embed
Progress spinner
rmdes
rmdes

@manton My AP fedify implementation already use micropub to create or update the post which is then formatted to be consumed by any AP inbox subscribed to me, I guess the next part is to build the client to server application so that I can natively talk to my AP server without any Mastodon API layer.

I’ll be trying this path with indiekit

|
Embed
Progress spinner
In reply to
manton
manton

@rmdes That’s great. I was just thinking of all the Mastodon-only clients that would be more flexible if adopting a standard posting API.

|
Embed
Progress spinner