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.
Addendum: Yes we know that you think ml/hexbear/grad are tankies and or .world are a bunch of liberals but it gets old quickly. Try and come up with new material.
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.