That's basically right yeah. Newly followed communities will have some backfill, like 50 posts I think, but no massive get-the-while-history automation exists.
The more active communities add content fairly quickly
Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.
That's basically right yeah. Newly followed communities will have some backfill, like 50 posts I think, but no massive get-the-while-history automation exists.
The more active communities add content fairly quickly
I've recently made it so that if you're back-filling a PieFed community the replies on the posts get retrieved too.
It's not possible with Lemmy because Lemmy chose not to provide a replies collection on a post. It looks like v1.0 of Lemmy might have an equivalent that we can use. https://github.com/LemmyNet/lemmy/issues/5283
Nice, that certainly helps giving these initial community imports some "life."
I figured out my lack of community posts was due to rapidly tearing down and re-deploying my piefed stack on the same domain. I think some federation began prior to the tear-down-then-re-deploy, so when the latest iteration began federating there were invalid signature errors for most activities since a new key was introduced. Result was a bunch of communities with no posts.
It would be nice to have some more targeted community import options as this thing matures. Something like an admin input for backfill value on the bulk import operations, or the option to to give a backfill value when doing specific community imports.