Wouldn’t that be better? Let me see if I can explain what I mean. Here on the fediverse each server is kind of restricted to what the user can post.
@[email protected] is for notes
@[email protected] for photos (wouldn’t be surprised if it used a note too)
Lemmy only for article objects.
Peertube for videos.
You get the idea.
This way of developing the #fediverse where each server only receive one kind of the objects accepted by #ActivityPub makes it more fragmented it, right? A server should send and receive all kinds of objects and should be up to the client to how to processes those objects.
If an user wants an Instagram-like app just create an account on any service and use and app with that UI, of lager they wanted to see more kinds of objects they should just use another client that supports Note, Article, etc. with the same account on the same server.
Ideally all server should have a shared API.
This fixes #fragmentation, the need to have multiple accounts if you are into multiple kinds of objects/content.
Imho, ActivityPub is a bad protocol that tries to accomplish everything, and ends up being bad at all of it. The spec is also ambiguous in a lot of areas. And major implementations don’t always follow the spec. All in all, it’s a miracle the fediverse even works as well as it does.
Instead of being “bad,” I consider ActivityPub as not being mature yet.
Other internet protocol like HTTP or email are also really basic on its early inception, but it later adding so many features and capabilities to be more modern and flexible.
Give it enough time, and ActivityPub will be mature enough for varied use cases.