Is this being worked on/looked at? I ask since the post mentioned discussion was happening with the .id admins but I haven’t seen any answers about whether that’s a priority (it seems Lemdro.id is the one that needs to federate with k.bin).

Just kinda bummed since I use kbin the vast majority of this time.

Edit: ah cool, quick turnarounds are sexy. Thanks @cole@lemdro.id!

  • cole@lemdro.id
    shield
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Edit: A fix has been deployed, and federation should work now. Unfortunately, kbin.social is taking its sweet time federating with us, it is probably overloaded. Lemdro.id is already accessible from other kbin instances such as fedia.io (https://fedia.io/m/android@lemdro.id)

    Hello! Admin here at lemdro.id. This is the result of several problems in the lemmy default reference nginx config. I am working on resolving this right now and should have it fixed within the next 30 minutes!

    • ubergeek77@lemmy.ubergeek77.chat
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Once you’ve finished updating it, can you share the changes you made to your Nginx config? If the default references have issues with them, I’d like to make sure mine doesn’t have the same problems.

    • ijeff@lemdro.idM
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Great news! Likewise, kbin.social doesn’t seem to be updating content from lemmy.world communities either (I’m seeing some a week late).

      • ubergeek77@lemmy.ubergeek77.chat
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Not sure if this is related, but I tried replying to a comment from a user on kbin, and my instance wouldn’t send the reply. They still have federated posts and top-level comments though, even mine. Maybe their queue is just overloaded.