You Should Know

BUT you can still upvote or comment on posts from different instances if you access them from within the instance your account is from!

So you don't need to create one account for each instance.

Edit: commented from a lemm.ee account

This is badly written - to someone who doesn't know any of this it reads like they're missing out on something. Yes there's !games@lemmy.world and !games@lemmy.ml - but you don't need an account on either to participate in both! You can just go there and browse, comment, etc.

Eventually one will become dominant, and it will all be fine.

Isn't that the whole point though? Not relying on a single entity by spreading out, but still being connected?

Fragmentation would be fixed by just integrating lemmyverse.net's functionality into lemmy itself (like in this github issue), allowing users to see the true user count/activity of comms and incentivise them to join the most popular one.

Needs to be done asap imo; comm discoverability is not good right now and is probably the single biggest hurdle for new users

But can I comment and reply in other instances? If that's true then I guess who cares?

When I see multiple communities on the same subject, I just subscribe to all of them. Either they'll eventually differentiate into their own unique spaces, or one of them will become the dominant one and the others will become fringe alternates. It's a good thing.

What you have identified is a feature, not a bug. It immunizes us against mods getting swollen egos and going on a powertrip.

IMO thats the beauty of a federated network

Ok so I'm looking at a post to You Should Know. When I look at the community info it says "You Should Know." The only way I know it's on lemmy.world is because it says you need to adhere to lemmy.world policies. I see nothing in the app (Jerboa) that indicates which instance it's on. What am I missing? If I am subscribed to a bunch of communities called "Games" how do I know which post comes from which community?

Lemmy does not currently allow for instance or user migration.

This should probably be high up on the list of additions. I like the idea of Lemmy but for things like getting support no one is going to use Lemmy if the entire community and all the posts can just disappear one day and all the history go poof.

Is this spez?

Misleading

So there is a !trees@lemmy.world and !trees@no.lastname.nz (pluss probably others)

The first is more or less r/trees the second I set up for therapeutic uses of 'trees' and shrooms

Each instance will have it's own ethos, mod policies and code of conduct. Choose your communities based on what gets posted to them.

The same could be said for [hypothetical] [!worldnewa@beehaw.org](/c/worldnewa@beehaw.org) and [!worldnews@lemmygrad.ml](/c/worldnews@lemmygrad.ml). They would be very different communities to read

As other commenters have mentioned, this is technically true but pretty misleading. This is viewing the fediverse through an inappropriate lens.

Your account technically doesn’t exist on other instances but it effectively doesn’t matter.

I like Lemmy a lot so far, and I’ve brought along a couple of friends… I do have a couple of questions though!

What happens if the server I’m on goes down for an extended period of time, or forever? Is my account data just gone? Or is that mirrored somewhere else?

I don’t think the post has a ton of merits for reasons that have already been described. That being said, there is one potential issue that I’m surprised that hasn’t been mentioned, which is impersonation.

Say someone takes the username jimbo on an instance somewhere and becomes super popular. Then someone else decides to create the same username jimbo on a similarly named instance and tries impersonating the other user. Sure, people can look and see “oh this isn’t that other jimbo” but you would have to look and see.

Probably not a major issue, but could theoretically become one.

This is the whole point...?

We need a more unified login experience. OIDC/Oauth would work wonders for this.

1. User registers at X lemmy/mastadon/peertube instance (activitypub app, [APA]) and gets malloc@lemmy.xyz
2. Users visits Y APA
3. Logins to Y APA using X user
4. User redirected to X APA instance to login (knows user registered at lemmy.xyz)
5. Upon successful login, user returned to Y APA

User now able to browse/post/comment in Y APA without having to manually go through original APA app where user account lives.

Basically each APA acts as its own IdP (identity provider); and would go a long way in improving user experience and reducing frustration.

If you are not familiar with this flow, then look at any web service with a login. They are usually accompanied by a Google/Apple/Facebook login option; and that’s that we are trying to replicate here. One set of credentials across the entire fediverse.