• BrogrumOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Also, I found this comment, though I don’t know whether this is (still) true:


      @VerifiablyMrWonka@kbin.social said:

      In order to catch up with a massive queue backlog a temporary hold on delivery to domains that are being problematic has been setup. Those other domains aren’t responding to kbin.social’s requests properly and so our own queues are getting backed up.

      It’ll all be back to normal soon. Once the queues are sensible we can reenable domains as they start becoming responsive to us.

    • BrogrumOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      It’s getting better. @meldrik@lemmy.wtf recently changed a setting in the nginx_internal.conf on lemmy.wtf (suggested herer) and we are now able to subscribe in both direction, I think.

      Not all older posts/comments are automatically federated, but you can manually “pull” them over by searching for the full source URL on the destination instance. Which I do from time to time.

    • MeldrikA
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      It is working now, but there is a big delay between things being posted on Kbin.social and then showing up here. I am pretty sure this is because Kbin.social is struggling with so many users.

      The same is true with lemmy.ml. Posts from there are also delayed.

      • MeldrikA
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        My comment actually showed up on Kbin.social immediatly!

        • BrogrumOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          But it looks like kbin.social isn’t federating (pushing/forwarding) comments which they received from us (lemmy.wtf) to other instances (e. g. lemmy.world) which have subscribed to their magazine, too. Or at least this takes very long.