this post was submitted on 11 Jan 2025
39 points (100.0% liked)

PieFed Meta

387 readers
24 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
 

We've brainstormed a few ideas for where we could focus our development efforts this year and created a post in a community for each idea.

This is the community: [email protected]

Now it's up to you to vote on each post to influence the priorities of those ideas! Please upvote those ideas that are important to you, ignore those that do not and only downvote when an idea seems like a counter-productive waste of time and energy.

Vote for as many ideas as you like but be selective. Something like upvote your top 10 ideas and downvote the bottom 5, that kind of thing.

top 13 comments
sorted by: hot top controversial new old
[–] [email protected] 5 points 1 week ago* (last edited 1 week ago) (3 children)

Just a heads up!

There might be a federation issue as I can't seem to see any of the posts even after checking with my 4 accounts (same username on differnet instances)

I tried using:

  • lemmy.ca
  • programming.dev
  • lemmy.blahaj.zone
  • feddit.uk
[–] Die4Ever 3 points 18 hours ago
[–] [email protected] 5 points 1 week ago (1 children)

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"

[–] [email protected] 2 points 1 week ago (1 children)

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.

[–] [email protected] 6 points 1 week ago

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).

[–] [email protected] 2 points 1 week ago (1 children)

Copy paste the post links in your search bar

[–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (1 children)

I'm currently using Voyager so tapping on [email protected] redirects me to:

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago)

I subscribed with my Lemmy.ca alt but couldn't get the posts: https://lemmy.ca/c/[email protected]

[–] [email protected] 4 points 1 week ago (1 children)

Yeah, as mentioned, Lemmy seems to have made a mess of bringing that community in. It looks like they got the community details - and know that posting is restricted to the mod, but they didn't fetch who the mod is. This meant that posts in the outbox were rejected, and all subsequent activity (that would normally cause them to resolve the missing posts) is being rejected too.

Screenshot (these activities are all Likes and Comments):

Full-size image link: https://postimg.cc/3481xLdq

[–] Die4Ever 2 points 19 hours ago
[–] [email protected] 3 points 1 week ago (1 children)
[–] [email protected] 2 points 1 week ago* (last edited 1 week ago)
[–] [email protected] 2 points 1 week ago