this post was submitted on 11 Jan 2025
41 points (100.0% liked)
PieFed Meta
624 readers
1 users here now
Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.
Wiki
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's nothing technically wrong with the outbox for that community. This can be confirmed from a command-line, by doing:
curl --header 'accept: application/activity+json' --location https://piefed.social/c/piefed_2025/outbox | jq .
I was also able to get it from my dev PieFed instance without issue.
So Lemmy is shitting the bed when processing the outbox.
Possible reason 1: the posts also contain replies in PieFed outboxes (but Lemmy should just ignore that field, and not all posts have replies)
Possible reason 2: the community is restricted to posts by the mod (but that shouldn't affect things)
Possible reason 3: "Lemmy reasons"
I thought content simply didn't federate retroactively, but only started when the first user from an instance subscribed the community. I'm probably wrong, but then again this seems to indicate I might be right.
When you first fetch a new community, you should always get the most recent posts (albeit without votes, etc). This is a different kind of federation than what happens when you make a post for the subscribers of a community to see - that content is being pushed out, whereas getting recent posts from a new community is being pulled in from community_name/outbox (which is just a big JSON file).