The image is from my Subscribed feed for this instance and another one (same subs on both).
I've also noticed things like https://feddit.nl/c/trendingcommunities having 26 posts, but https://communick.news/c/trendingcommunities@feddit.nl having zero, and https://lemmings.world/c/wwdits having newer posts than communick.news' version of it.
I don't know what happens behind the scenes, so maybe there's just some catching up to do, but was wondering if anything more fundamental was going on.
Thanks.
It's because of how federation works. It all depends on the time that someone in our instance starts following the remote community. If you just subscribed to it, we will start seeing any posts from now on, but not the ones in the past.
I'm fairly certain that's not true. If you subscribe to something, you won't get comments or upvotes, but you'll typically get posts. I can see that I'm literally the only subscriber on this instance to many communities, and I can see all the previous posts.
Moreover, for many of my subscriptions it's the other way around. I subscribed to everything on 2023-08-04 (i.e. the 4th of August) - I can usually see the posts up to that point, but nothing after.
Some examples of Communities I've subscribed to that have new posts at their instance but not this one:
!badrealestate@feddit.uk
!asklemmy@lemmy.ml
!raining@sh.itjust.works
!trendingcommunities@feddit.nl (this is the only one where there's no posts, past or present)
!wwdits@lemmings.world
I'm seeing now though all those Communities have their subscription set to 'Pending', so maybe that's the issue. But I don't know how to move it past that point (I don't think it ever changes by itself).
Ah, ok. I understand it now.
It seems that there are some federation issues, possibily related to this bug. I am trying to see if there is something I need to do on our end or if it is a matter of getting in touch with the other instance admins to see what can be happening.
Thanks for letting me know, I will post an update as soon as possible.
Hey, so I've looked at some of the instances and I've been talking with admins of others: it seems that indeed the problem is related to the bug on version 0.18.3. It is possible that a post might show up on our instance if the original author tries to edit and save it again, even if no change. The edit will trigger a new attempt for broadcasting the message and the message should show up again.