7
Truncated community view
(piefed.social)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Aug 2025
7 points (100.0% liked)
PieFed help
1068 readers
24 users here now
It's seems right that we should have a local community to help us all with PieFed
Rules
Be kind! We're all learning
founded 2 years ago
MODERATORS
Community migration doesn't backfill like this. Instead, it simply reassigns all the posts that the instance has in the old community to the newly migrated community. So, if there are important posts/comments that aren't federated over yet, you should force that federation before going through the migration.
To force federation of a post/comment in piefed, go to the community on its home instance and locate the post/comment that you want to bring into piefed. Copy the canonical link from that post comment. This is the link that the little fediverse icon points to (it's a little version of this logo):
Then, go over to the community on piefed, and near the bottom of the sidebar, there is a link to "Retrieve a post from the original server". Click that and paste in that canonical link you grabbed. Piefed should go out and pull over the post/comment that the link points to. One thing to note is that you can't pull a comment that is a reply to another comment without first pulling what it is in reply to.
Some posts seem to not be retrievable, yet they exist when you follow the canonical links and the Lemmy instances aren't blocvked.
This one for instance:
https://pawb.social/comment/13985010
Any idea why?
That case would be because piefed.social is defederated from pawb.social, preventing the federation.
Right okay I undertand. Thanks!
Wow thanks. It's less obvious than the Youtube video makes it out to be.
Your comment should be stickied somewhere.
EDIT: I'm retrieving posts from the original SDF community one by one (good thing it's a small community with low bandwidth ๐) and I notice that, while the posts appear, the original downvotes/upvotes aren't. copied over. I don't really care, but I figured I'd mention it.
This is a limitation of the api and is also what happens when force-federating content from lemmy to lemmy instances as well. TBH, including all the vote information for each post/comment is probably overkill and would bloat the api responses a lot.
When you are using an app/frontend to browse lemmy/piefed, the vote totals are displayed, that is simple enough. However, on the backend, each vote has a bunch of information attached to it like user/instance/timestamp/etc. All that information is not included when force-federating content, thus the lack of votes after being federated over.
Well, the overall score was reflected on those original posts piefed.social mirrored by itself. So it did work at least once. It's those extra posts I forced Piefed to retrieve manually that all came with the default score of 1.
Like I said, it doesn't really matter. But ideally when I finally decide to relocate the communities, I'd like the Piefed copies to be identical. But the scoring is not important: what I really care about is the content and that made it across, now that I finished the retrieve job manually. So it's all good.
Well done