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.

@Mastodon@mastodon.social is for notes

@pixelfed@pixelfed.social 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.

  • TheFederatedPipe@fedia.ioOP
    link
    fedilink
    arrow-up
    4
    ·
    6 days ago

    I haven’t developed anything with #ActivityPub, but have read a little bit of the spec. I would love to hear the take from developers making use of it.

    (Sorry for the mention in any case)

    @silverpill@mitra.social

    @hongminhee@fosstodon.org

    @dansup@mastodon.social

    @thisismissem@hachyderm.io