this post was submitted on 05 Mar 2024
3 points (100.0% liked)
Fedia Discussions
2 readers
4 users here now
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Remote magazines only get new posts from the point in time when they are created locally. It won't pull old posts off the originating server.
~~Update: Maybe not. I thought that's how it works but I see content in the Florida one. Curious. I don't know then. ¯\(ツ)/¯~~
Update 2: comment from e-five could explain how old posts show up on new communities.
It should receive data from any activity at the other community. The problem seems to be Fedia not receiving data from certain communities.
It's not just the state communities. There's a lot of communities that are missing posts. Even ones that happened recently. For instance: https://fedia.io/m/netsec@lemmy.world
And I've noticed some servers aren't federating anything, like lemy.nl: https://fedia.io/m/nieuws@lemy.nl
I am not sure what is going on with some of the lemmy.world communities - some do seem to be having issues like netsec, while others like https://fedia.io/m/news@lemmy.world are humming along very well. I'll keep poking at it.
I mentioned in the adjacent post but if you do see magazines acting oddly, it could be there are no local subscribers. Hopefully we get a UI fix in soon with the PR I had mentioned, because it's a bit of a bad user experience now. (I noticed world from lemmy world on debounced's instance was getting no posts, or rarely a post with no likes, and subscribed, and suddenly everything came in fine.) So probably a good idea for people, if you want to see posts from somewhere, make sure to subscribe.
(This was technically always true, but a while back admins were auto subscribed so a magazine would always have 1 subscriber. That changed, and that change was even backported to kbin by ernest, so it should be like that back in kbin too for new magazines.)