• Queen Bee@honeyhive-u4873.vm.elestio.app
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    vor 3 Jahren

    Federation is not perfect between kbin and lemmy. On kbin instances, if the server pulls some federated content that it isn’t quite sure what to do with, it drops it into m/random. Same thing happens if it’s missing any sort of meta data AFAIK

    • Rhaedas@lemmy.one
      link
      fedilink
      arrow-up
      2
      ·
      vor 3 Jahren

      Would it resort it into the original posted area if it later grabs the metadata, or is the push a one time thing?

      • Queen Bee@honeyhive-u4873.vm.elestio.app
        link
        fedilink
        arrow-up
        2
        ·
        vor 3 Jahren

        AFAIK it doesn’t go back and update old posts. So if the connection is fixed and the bridge between these two services is rock solid, everything before that won’t be changed. It will only affect future posts.

        • Rhaedas@lemmy.one
          link
          fedilink
          arrow-up
          2
          ·
          vor 3 Jahren

          In retrospect that makes sense, the last thing we want is a recursive effort to try and update things all the time.

  • TheSaneWriter@vlemmy.net
    link
    fedilink
    arrow-up
    3
    ·
    vor 3 Jahren

    Might be something acting up with the federation. I think kbin.social enabled Cloudflare, which is blocking some parts of the federation scripts, leading to broken pulls like this. Don’t worry about it on your end, there’s nothing we lemmings can really do about it.