Lemmy.zip has not federated yet. If you subscribe to the community, it should federate with it and pull the 20 most recent posts. Don’t quote me on this, it’s just what I’ve read.
Erm… sort of. The instance federates with other instances when it is created. But two instances being federated does NOT imply that every post/comment gets replicated between them. Rather, a given community starts replicating when the first subscriber on an instance subscribes.
If you mostly subscribe to popular communities from a big instance, you won’t have encountered this just because it’s unlikely that you’ll have been the first to sub to any community. But if you get into niche communities, newly created communities, or switch to a smaller instance… you may be the first to subscribe and then more or less what you’re describing takes place. But it’s about subscription and replication of a particular community, federation between the instances must have been set up already for you even to find and subscribe to the community in the first place.
Thanks for this…indeed the community I have on ml still doesn’t show anything in lemmy.zip
Is there any way to see older posts in a situation like this? I created my own instance, and am only seeing the most recent handful of posts from communities I subscribed to.
I think if you search your small instance for a post URL it fetches the post content from the server that hosts the community. Or maybe you have to visit the post url on your server (which has a weird format like
https://your.instance/@other.instance/post/idor something vaguely similar.There’s no mass backfill, you could maybe script something using this. But I’d advise to do it sparingly, like the last 100 posts for your favorite communities or something. This kind of thing could induce unreasonable load on the community server if lots of people did it, which is why Jerboa doesn’t backfill by default.
Also note, this is a temporary problem. How often do you scroll back more than a week? By next week, your server will have that much history.
must run on linux?
I’ve noticed the same thing when I switched to my newly set up personal server.
