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/technology@beehaw.org 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

  • dannekrose@kilioa.org
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    @Treedrake

    Edit: ok, I think I get it. So if someone from a random instance posts to e.g., technology@beehaw.org, and that instance doesn’t know about kbin.social, it won’t get pushed to this instances representation of the technology@beehaw.org 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 technology@beehaw.org, 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
      link
      fedilink
      arrow-up
      7
      ·
      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
        link
        fedilink
        arrow-up
        6
        ·
        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.

          • Kichae@kbin.social
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            Eh, it’s not much of a downside in an active community. The model is push once at time of publication, there are other systems in place that republish content and help it propagate through the network.

            On kbin, there’s a “boost”… well, it’s not really stylized as a button, but there’s a “boost” feature, which acts to republish posts or comments and allows them to reach newer subscribers. I’m not sure how it works on Lemmy, as there’s no explicit boost, but there are mechanisms there to renew active back content.

            It all just means we, as users and members of communities, need to take on a little bit of responsibility for ensuring that interesting or valuable content propagates.