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/[email protected] would become https://piefed.social/c/fedigrow , with all the existing posts and comments
- you all would subscribe to the new [email protected] , 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/[email protected]), 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/[email protected]
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.
Ok, I watch the video with presenting the feature. @[email protected], what is the AP representation of posts?
All the posts are reassigned to the local piefed community. From the perspective of remote instances, PieFed just got a new community with a whole lot of content in it.
I just checked one post from lemm.ee that was migrated to piefed. You are keeping two different objects with the same id, but altering the content to change the audience. I’d have to agree with @[email protected], that would definitely qualify as falsification.
Thank you for your magnimity
What about “as:audience” attributes from the original “Create(Page)” activities? Does this mean that you are completely rewriting history?