I doubt it. While the server to server communication is standardized with ActivityPub, the server to client (app) communication isn’t. This means different Fediverse apps have different APIs to login, fetch and create posts and so on. It’s unlikely that we’ll ever have a standard API here, because the apps work diffently and have different needs for their APIs. Maybe some kind of common denominator, but that probably wouldn’t be feature complete on most apps.
So the one app to rule them all would have to created custom API Implementations and UIs for every Fediverse app, which would be a loooot of work and probably a worse experience than specialized apps.
So there is apparently a server to client protocol/spec/API defined on activity pub. No one uses it, but maybe they should be. I don’t know. I’ve hassled one of the AP authors (Evan) about it and they said they’re writing a blog post about it.
I doubt it. While the server to server communication is standardized with ActivityPub, the server to client (app) communication isn’t. This means different Fediverse apps have different APIs to login, fetch and create posts and so on. It’s unlikely that we’ll ever have a standard API here, because the apps work diffently and have different needs for their APIs. Maybe some kind of common denominator, but that probably wouldn’t be feature complete on most apps.
So the one app to rule them all would have to created custom API Implementations and UIs for every Fediverse app, which would be a loooot of work and probably a worse experience than specialized apps.
So there is apparently a server to client protocol/spec/API defined on activity pub. No one uses it, but maybe they should be. I don’t know. I’ve hassled one of the AP authors (Evan) about it and they said they’re writing a blog post about it.