How come this Lemmy community only shows the last 15 posts / 10 months worth of posts on Piefed?
This community or this community (from the same Lemmy instance) too are clipped, but they both show a year’s worth.
Does it have something to do with the date at which the first PieFed user join them?
I know Lemmy instances only start mirroring a community hosted on another instance when someone on that instance joins it. But after that someone joined and the instance is done mirroring the community, the whole of it is browseable.
If I had to guess, I’d say Piefed instances only mirror the 15 last posts after the first user joins, or a years’s worth, whichever applies. Correct?
And if so, does this also apply to native Piefed communities? In other words, does Piefied “disappear” older posts in Piefed communities?
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