I think one of my problems with the fediverse right now, is that the client application and backend activity pub engine are too intertwined.
For instance, if I want to use something like Bookwyrm I'd need to spawn a new service and a new identity to engage with that content, rather than log into a client with my existing Mastodon ID.
I realize this might be more of a Matrix-brain of thinking about it, but it just seems more rational to me to split it that way.
@halfy I think this is basically what GoToSocial is meant to address?
@joepie91 Also, critically as at a social level it doesn't stop developers thinking about their applications as complete silo'd stacks and making breaking changes with GTS, and I'd imagine running "just" the client for some projects is non-trivial.
It feels like someone is working towards a solution at a technical level, but I think my point is I disagree on a fundamental level with how things are structured.
@joepie91 Hm, seems halfway there. It solves the problem of separation partially, but then implements "the mastodon API" which sounds rather incompatible with the rest of the 'verse.
I wouldn't mind something that implemented "Activity pub + these extensions to make things like Mastodon work"