So the community (users) can move, but I just realized that when an instance shuts down the community (posts) limps on, preventing the community (posts) from actually dying and the community (users) from moving on.

For instance, if you asked me, a lemmy.world user about moviesandtv@lemmy.film I would see, https://lemmy.world/c/moviesandtv@lemmy.film

But if you ask a sh.itjust.works user they see, https://sh.itjust.works/c/moviesandtv@lemmy.film

And lemmy.ml users see, https://lemmy.ml/c/moviesandtv@lemmy.film

We all see different versions of the same community (posts).

I think https://github.com/LemmyNet/lemmy/issues/4619 would fix this.

Re Concentration I’m not concerned that it is as of yet a problem. However I do think it is also a larger problem for Mastodon and other user-centric platforms than it is to Lemmy and other community-cetric platforms.

If a Mastodon user wants to leave their server there are migration pains. If your server makes a controversial change, you may have to migrate. As a follower if something goes wrong I have to remember that I was following Ada & Bob, but maybe Bob now goes by Bobby.

However as a Lemmy user I can just abandon my server and be done with it. If my server makes a controversial change, I can just leave. As a community follower can watch as Star Trek Memes becomes Risa, or Risa becomes Ten Forward. The names changed completely but it’s easy to find my community again.

Sure Reddit and Lemmy are different technical stacks, but neither is doing anything particularly unique or complicated.

If Reddit wanted to federate it could. It would take some work but it would be an achievable task in a reasonable amount of time.

Perhaps scaling or stability issues. I’m not sure the Fediverse is ready to handle the number of actions a site like Reddit handles. Then again I’m not super well versed on that part of the Lemmy software, so maybe it would be fine.

Is the problem account making or data having persistence/backups?

Or is the issue having an account on service A, service A dieing and then when you create an account on service B you have to start over again, so we need to improve account portability?

I guess I also wonder… Is that a real problem for Lemmy? For Mastodon where you follow users sure, but does anyone care about their Lemmy account?

And what’s stopping that from happening now?

I assumed, perhaps incorrectly, that servers die because they are difficult to maintain. This is perhaps especially true for kbin/mbin based servers.

I suppose for enough money some might be willing to maintain, but I’m not sure it’s that simple.

Is there a solution to make the whole ecosystem mature and professional?

Certainly having everyone on one instance isn’t the way to go.