To be fair, lemm.ee didn’t really act as host to any major communities to begin with. So communities aren’t really the loss here, and it could be that having at least a few big active communities on an instance is a key part of maintaining its long term viability.
Also, all the text posts and comments from lemm.ee will still remain on other instances. I’m sure the instance could also back up content, if the specific admin so desired to re-host.
Yeah the biggest communities seem to be movies and television, and my guess is that they’ll be gobbled up by lemmy.world. But every community migration like currently looses subscriber members, and split communities mean a lack of interaction. Social network require a critical mass, and also benefit from centralization. While federation works great for users there isn’t a real solution for communities yet. There is a lot of randomness involved, like who gets to be the first to make a community might be a bad mod in the long term. For example the reddit r/climate mod is a climate skeptic. Not sure if there is any better solution.
I’m just wondering how the best design for this problem would look like. Maybe the mod of a community could have some kind of key that he can transfer to another instance and automatically transfer all the user subscriptions and link the post history with them.
For me, the bigger problem with how Lemmy is federated is the way comments and posts have unique IDs for every instance. You can’t easily find a comment or post from one instance on any other instance. With users, you just have /user/username@instance, what we need is /post/###@instance or /comment/###@instance. Instead, we just have /post/### and the ### is different everywhere (I think it’s just sequential for every post/comment the instance federates).
Maybe there’s some reason they did it this way, but it feels like the better solution is to have the original host instance decide the number, then every other instance just use their number and their @instance.
To be fair, lemm.ee didn’t really act as host to any major communities to begin with. So communities aren’t really the loss here, and it could be that having at least a few big active communities on an instance is a key part of maintaining its long term viability.
Also, all the text posts and comments from lemm.ee will still remain on other instances. I’m sure the instance could also back up content, if the specific admin so desired to re-host.
Yeah the biggest communities seem to be movies and television, and my guess is that they’ll be gobbled up by lemmy.world. But every community migration like currently looses subscriber members, and split communities mean a lack of interaction. Social network require a critical mass, and also benefit from centralization. While federation works great for users there isn’t a real solution for communities yet. There is a lot of randomness involved, like who gets to be the first to make a community might be a bad mod in the long term. For example the reddit r/climate mod is a climate skeptic. Not sure if there is any better solution.
I’m just wondering how the best design for this problem would look like. Maybe the mod of a community could have some kind of key that he can transfer to another instance and automatically transfer all the user subscriptions and link the post history with them.
For me, the bigger problem with how Lemmy is federated is the way comments and posts have unique IDs for every instance. You can’t easily find a comment or post from one instance on any other instance. With users, you just have /user/username@instance, what we need is /post/###@instance or /comment/###@instance. Instead, we just have /post/### and the ### is different everywhere (I think it’s just sequential for every post/comment the instance federates).
Maybe there’s some reason they did it this way, but it feels like the better solution is to have the original host instance decide the number, then every other instance just use their number and their @instance.
Pretty sure that was on the bug list 2 years ago.