It looks like some issues may arise if/when an instance's domain name changes. Is there any way we can change federation so that we don't need to rely on such a central point of failure?

you are viewing a single comment's thread
view the rest of the comments

[–] rglullis 1 points 1 day ago* (last edited 23 hours ago) (1 children)

AFAIK, "community migration" is done in PieFed by having the target instance making a request to the source one to change, and if the owner authorizes it then it PieFed recreates the actor and its objects on the target instance. Then it is up to the owner of the source community to delete close the source community.

My objection is to this recreation of the objects. If someone creates a post on "community@alpha" and the moderator decides to move to "community@beta", history is being recreated and it makes "beta" with activity that is not original. Also, having the consent from the community owner is not enough, because it ignores the fact that the members of the alpha community might not be interested in being associated with beta.

[–] Pamasich@kbin.earth 2 points 23 hours ago

Oh yeah, this does not sound okay.

If user@delta creates a post on community@alpha, their post lives on delta, not alpha. Community@alpha should not be able to unilaterally decide that the post should instead live on beta. Delta needs to be the one to decide that.

Sorry for the political analogy, but this sounds to me like Russia and the US deciding on Ukraine's future without involving the latter.