What do you think some of the fediverse's primary stumbling blocks are? - eviltoast

For those that have poked around other fediverse stuff beyond Lemmy, and been around the spaces awhile, what’s stuck out to you as stumbling blocks, or basic user experience fumbles? Which parts do you think may be technical, and which may be cultural?

  • Feathercrown@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Would be nice if people could keep a distinction between their instance, and their identity, so that the identity could refer to their own domain, for example.

    This is one of the ideal use cases for Solid, in development by MIT and Tim Burners-Lee. Basically, you host a central store of data, including one or more user accounts, and allow access to it from other services.

    • mnrockclimber@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      This was the original premise of app.net - a social service from years back. They built a “social backbone”. They offered you a single place where your identity and friends were housed. Other people could build apps on top of the backbone.

      So you would join say a clone of Instagram and all your friends were still there. And your account still worked. Or they had a Twitter clone. Same deal. It was a single sign-on social account/identity/social graph that was separate from the apps. So things could just plug in.

      Worked great. But it was a paid service. And came out right at peak Facebook so it died off.

    • Extinction Studies@hcommons.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      @Feathercrown @modulus

      I’d be more comfortable with self-hosting my actual data somewhere, and just having an instance or the central store point to my data. I’d want to get to apply rules for who gets access to my data. It would be a lot easier to spin up a small data store with a few tools on it than a full instance.