id bet they are equal. its likely a similar backend/database process of just updating all the records of a ‘remote’ community into a local one. this instance has been up for a few years now, and so has a good copy of a lot of remote content.
Thanks, the new community looks great! Cool that you were able to migrate most of the existing content.
However, like with Piefed, it seems that Lemmy users are currently not able to see the migrated posts. If someone replies to a Lemmy user’s post or comment which was migrated, I assume that user would not receive a notification, correct?
yep, mbin.
id bet they are equal. its likely a similar backend/database process of just updating all the records of a ‘remote’ community into a local one. this instance has been up for a few years now, and so has a good copy of a lot of remote content.
Thanks, the new community looks great! Cool that you were able to migrate most of the existing content.
However, like with Piefed, it seems that Lemmy users are currently not able to see the migrated posts. If someone replies to a Lemmy user’s post or comment which was migrated, I assume that user would not receive a notification, correct?
We could easily test this if you leave a comment on one of my posts which was migrated.
Is there some way to push the migrated posts to federate with Lemmy instances?
If not, and if the original posters never see new replies, are there sufficient advantages to warrant leaving the comment sections open?
It feels similar (though not identical) to projects which mirror posts and comments from Reddit. Sure, the content is there, but the people aren’t.
Would it be possible to lock all of the threads which were migrated, essentially preserving a “read-only” archive?