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

[email protected]

Voting on the PieFed roadmap for 2025 is now open! (piefed.social)

submitted 3 months ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 3 months 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 3 months 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).