Presentation of the feature: https://piefed.social/post/667045
Example of successful migration: https://lemmy.dbzer0.com/post/45876492
Our next step would be to give this feature a try. What would basically happen is that
- we would lock our community to prevent integrity issue during the migration
- https://piefed.social/c/fedigrow@lemm.ee would become https://piefed.social/c/fedigrow , with all the existing posts and comments
- you all would subscribe to the new !fedigrow@piefed.social , and then continue as usual
Should the migration not work, we would still be able to use the current community, and then manually migrate elsewhere.
The one caveat is that from Lemmy instances, the community doesn’t have show old posts (see https://lemm.ee/c/barcelona@piefed.social), but if you were restarting a community from scratch you wouldn’t have access to your old posts anyway.
Other federated instances like feddit.online would also see the posts and comments on the new community: https://feddit.online/c/barcelona@piefed.social
The objective of this post is to address any questions or issues before we move forward. We are probably going to leave it open for 48 hours, and then reassess based on the community feedback.
Excuse my pedantry, but from the point of view of ActivityPub, it is.
Any remote instance sees your posts to any community as a
as:Announceactivity. All that the community is doing is boosting your comments/posts, and that can be done by anyone else.