Looks like Kbin is running a pretty huge federation backlog, as it’s taking several hours for comments to federate out. I’m not knowledgeable about how these servers work, but is it teetering on collapsing or something?

  • FaceDeer@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    10 months ago

    I just set up an account at fedia.io, which is an mbin instance. When I ran the script posted over here to copy my subscriptions I had 111 subscriptions succeed and 49 fail. I’ve been checking the ones that failed and they’ve all been ones that haven’t had anyone post in them for 5 months or more, so I’m guessing those are “dead” anyway. Seems not too bad, I’ll see how it goes I guess.

    I posted this same response from both of my accounts, I’m going to watch to see how well it federates back and forth.

    • s0ckpuppet@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      Yep actually did the same myself with fedia and that script. Also had some fail which I think were likewise abandoned.

    • s0ckpuppet@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      Yeah the comments are not federating across fedia/kbin. I’m only seeing your comments on this thread when you’ve posted them on the server I am currently viewing. Even 8 hours after you commented.

      • FaceDeer@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Weird. Your initial comment federated, since I was able to see it from both instances. All these responses to it did not, though.

        • s0ckpuppet@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          10 months ago

          Oof. This definitely needs to get sorted out asap. It would be the death of a federated platform centered around discussion. It’s kinda one of the main tasks.