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.

you are viewing a single comment's thread
view the rest of the comments

[–] bjoern_tantau@swg-empire.de 13 points 2 days ago (1 children)

The only problem that I see with this is that images and especially videos take up vastly more space than plain text.

And does ActivityPub include client APIs? I haven't looked at it, but my completely unfounded impression has been that it only handled server to server communication.

[–] TheFederatedPipe@fedia.io 2 points 1 day ago

That is a fair point, and I don't have the answer. Maybe use technics that @peertube@framapiaf.org uses like torrenting (or another way of decentralized storage), I guess you could use a cdn/object bucket?