this post was submitted on 25 Aug 2023
97 points (100.0% liked)

Fediverse

17788 readers
8 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
97
What do you think some of the fediverse's primary stumbling blocks are? (lemm.ee)
submitted 1 year ago by ALostInquirer@lemm.ee to c/fediverse@lemmy.ml
56 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] Feathercrown@lemmy.world 2 points 1 year ago (2 children)

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 2 points 1 year ago (1 children)

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.

[–] Feathercrown@lemmy.world 1 points 1 year ago

Ooh neat. Too bad that it was paid. And centralized/private for that matter.

[–] aka_quant_noir@hcommons.social 1 points 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.