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.

  • rglullis@communick.newsMEnglish
    3·
    1 year ago

    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.

    • rglullis@communick.newsMEnglish
      1·
      1 year ago

      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.