Comment on Can we make federation less dependent on domain names?
Pamasich@kbin.earth 1 day agoIs Piefed implementing this in some weird way?
Iirc previous work on this in the fediverse involved a very clear way of doing it that makes sure to address the issue you're bringing up there.
The idea is that you send activities to announce the move and mark the original actor as having moved to the new actor (and the new actor as being the new home of the original actor). Instances then verify this by whether that actor relationship is specified correctly on both sides (does going new actor -> origin actor -> new actor lead back to where we started from?).
Is that not also Piefed's implementation? Because if it is, I don't see your scenario being viable. Since the move needs to be acknowledged by both sides, it cannot just be faked.
rglullis@communick.news 1 day ago
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 the/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.
Cracks_InTheWalls@sh.itjust.works 38 minutes ago
I almost feel like someone needs to do a write-up of the 196@blahaj.zone debacle - while not a 1-for-1 example (it wasn’t a migration attempt that functioned the exact same way as it would with PieFed), it’s a good case study for userbase-community owner-instance dynamics that should be considered, specifically the bit in your last sentence.
Pamasich@kbin.earth 1 day 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.