I’ve been seeing this for quite a bit, and thought it’d resolve itself once CloudFlare was taken off, but I’m still seeing it on many external communities from e.g. Lemmy. Not all posts or comments are visible from Kbin. Any idea on what’s going on?

Edit, clarification: when I visit e.g., https://kbin.social/m/[email protected] the above mentioned sentence shows up, and I’m not able to see threads created even 13 hrs ago, like this one on the original instance https://beehaw.org/post/927935?scrollToComments=true. New content doesn’t seem to be pushed to this instance at kbin.social. This is the issue I’m referring to.

Edit 2: This is probably the answer: https://kbin.social/m/kbinMeta/t/131241/What-s-up-with-The-magazine-from-the-federated-server-may#entry-comment-517045

  • Treedrake@kbin.socialOP
    0·
    1 year ago

    Thanks for the clarifications. Regarding 3, why does some new content from e.g. [email protected] gets pushed to an instance like lemmy.world, but not all new content? I mean, if some content gets pushed it seems to be aware of that instance. Or is it random which content gets pushed? Does this mean that the other instance will never get all new content? This seems like quite the issue?

    Edit: ok, I think I get it. So if someone from a random instance posts to e.g., [email protected], and that instance doesn’t know about kbin.social, it won’t get pushed to this instances representation of the [email protected] magazine?

    • dannekrose@kilioa.org
      1·
      1 year ago

      @Treedrake

      Edit: ok, I think I get it. So if someone from a random instance posts to e.g., [email protected], and that instance doesn’t know about kbin.social, it won’t get pushed to this instances representation of the [email protected] magazine?

      Correct. It’s only “pushed once” by the instance that the creator’s account is on. Of course it will push to the source of truth, but it will only push to other instances it knows are also following that magazine since it doesn’t necessarily know all of the instances that follow that magazine. In your example, yes, if the creator of the content (which in this example is an account not on beehaw.org) posts to [email protected], their instance will push to beehaw.org and others, but if it doesn’t know that kbin.social has any followers of the magazine/community, it won’t push to kbin.social.

      One other possibility is that the 3rd-party instance does know about kbin.social (for example), but has blocked (defederated with) kbin.social OR kbins.social has blocked that 3rd-party instance, my expectation would be that such content won’t show up on kbin.social’s “copy” of the community.

      • Treedrake@kbin.socialOP
        1·
        1 year ago

        So it’s basically working as intended? It does feel like an annoying “issue” though. Thanks for explaining anyhow!

        • dannekrose@kilioa.org
          1·
          1 year ago

          @Treedrake

          You’re welcome!

          Yes, it is working as intended. The idea is that each instance is responsible for pushing content once, then it’s the responsibility of the receiving instance to process and display the content to the relevant users/accounts.

          As a side note, if everything was “re-pushed” out, the load becomes even more on the “source of truth” for larger communities with wide federation and a lot of new content generated locally and remotely. I could see this being leveraged to take down servers by simply spamming really large communities (with large federation) with small content forcing the “source of truth” to now “re-push” the content to every server that is knows about for every single new comment, or reply, or post.