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.

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

[–] rglullis@communick.news 4 points 4 weeks ago (9 children)

Not in favor.

[–] Blaze@lemm.ee 8 points 4 weeks ago (8 children)

Could you please elaborate why?

[–] rglullis@communick.news 6 points 4 weeks ago (7 children)

PieFed has the tendency to add features that are are not compatible with ActivityPub in general (flairs, multi-communities) and I am not convinced it is ready to have a large influx of activity. It's one thing to have a server with lots of users receiving notifications, it's another to have the same server also responsible in sending a large number of notifications whenever it needs to announce a new comment or post.

[–] Blaze@lemm.ee 4 points 4 weeks ago

Fair. I'll edit the title so that people can also suggest the instances they would like to move this community to.

load more comments (6 replies)