transcript
A picture of the Ben Affleck Smoking meme, with the caption “Me seeing people on reddit telling other people to go to lemmy.world”
A picture of the Ben Affleck Smoking meme, with the caption “Me seeing people on reddit telling other people to go to lemmy.world”
I haven’t looked at the Lemmy codebase but here’s my thoughts on why they don’t “just” fix this.
Unless the database is designed for easy migration from it can be a very large task to modify the database layout, as you nearly have to refactor everything.
One way to solve this is that all posts/comments/votes uses an UUID as primary key instead of auto-incrementing IDs.
Hi, so moving in AP (ActivityPub) doesn’t really work like that.
Essentially, every action (like, follow, create etc) is an
activity, “moving” something sends a “move” activity to every follower of an actor (group, user etc), which will make them follow the new account.So moving a community is really just making everyone unsubscribe from the old on, and subscribe to the new one, set the old one as read only, and setup a redirect (“This community has moved to !newcomm@instance”). The old comm will stay, and it can be browsed.
Take a look at “nomadic identity” though, its a bit more similar to what you are talking about.
Mod actions don’t even federate properly yet, you have to have a local account to mod properly. And post pinning only works when the stars align. With all those basic features having issues, comm migration is nowhere near the top of the priority list.