In the typical web marketing infrastructure, a company signs up for an email account for private messages, Twitter/X account for microblogging, YouTube account for video sharing, and Reddit for forum discussion.

With the Fediverse/ActivityPub model, currently a typical user might register a PeerTube account for video sharing, Mastodon for microblogging, and Lemmy for forum discussion. But the data under all those is the same infrastructure, right?

Facebook as a mature software platform has areas of its app for private messaging, microblogging, and video-specific content, all using one user account.

Is it likely that Fediverse apps will evolve toward a similar structure, where a person or company would only need one account and could push out content of all types there, and interact with others’ content with one account?

  • Ada@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I doubt it. I admin a lemmy instance and a regular fediverse instance, and I use them both very differently, because their interfaces lend themselves to different uses. Even though they can communicate with each other, trying to navigate a large number of lemmy groups from Hajkey would be annoying, and trying to follow specific users from lemmy would be annoying.

    An all in one app would mash that all together, which would probably be overwhelming and confusing

      • Ada@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Hajkey, which is a fork of Calckey/Firefish. If you’re unfamiliar with them, broadly speaking, it’s a mastodon alternative with a fancy UI

    • grahamsz@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      But the cool thing about open standards is that there’s a clear pathway to creating an everything app. Especially if decentralized ids gain some traction, then we could have an app that combines mastodon and pixelfed but presents the different posts in a sensible way.

      I can’t really wrap my head around what such an app could look like, but it’s much more feasible to build one than it would be with closed services. I’m hopeful that freedom to experiment without lockin will lead to some really neat ideas