FOSSDLE PieFedVoting on the PieFed roadmap for 2025 is now open!
submitted by
Rimu
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: !piefed_2025@piefed.social
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.
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
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).
Copy paste the post links in your search bar
I'm currently using Voyager so tapping on !piefed_2025@piefed.social redirects me to:
I subscribed with my Lemmy.ca alt but couldn't get the posts: https://lemmy.ca/c/piefed_2025@piefed.social
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
Recently I was on lemmy.world, subscribing myself to !sophie@piefed.social to make my future dog pics federate out. Initially the lemmy copy of the community had no mod but after a few minutes it did.
Seems like a bug on Lemmy's end. In PieFed the retrieval of the mods happens before the backfill so we are unaffected by something similar.
Anyway I'm more interested in having PieFed accounts vote, Lemmy users won't have enough experience using PieFed to have a feel for what needs to be done.
Amazing!
@Snoopy@jlai.lu