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/casualconversation@lemm.ee would become https://piefed.social/c/casualconversation , with all the existing posts and comments
- you all would subscribe to the new !casualconversation@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 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.
Well, someone’s gotta be the guinea pig!
I have no idea what, if any, compatibility issues exist between Piefed and Lemmy instances today, as I don’t normally use any communities on instances running Piefed. Might be a good idea to ask the PieFed people or piefed.social admins about any known issues, or check the Piefed issue tracker:
https://codeberg.org/rimu/pyfedi/issues
e.g.
https://codeberg.org/rimu/pyfedi/issues/658
Like, for a community that relied heavily on post flair to make the community work, that might be a substantial issue.
I’ve been using Piefed for the last few weeks as my daily driver, no issue so far.
Lemmy doesn’t show flairs anyway, so no community can reliably use them, they’re just accessory “nice labels” at the moment.