Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

General discussion about devices is welcome. Please direct technical support, upgrade questions, buy/sell, app recommendations, and carrier-related issues to other communities. Join Here: !android@lemdro.id https://lemdro.id/c/android

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

    I faced the same issue with other new communities as well and I think it’s because of the new lemmy version 0.18? and it’ll be fixed

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

      It’s strange, I’ve seen other instances that have upgraded to 0.18 that have no issues whereas some have issues. I’ve also seen some that aren’t federating even on earlier versions. lemmy.blahaj.zone upgraded to 0.18 but seems to still be federating just fine with Kbin, but lemmy.ml seems super broken with Kbin. Hopefully it gets resolved soon, I’ve run across several communities I want to follow but can’t due to federation being broken

    • Pamasich@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      It doesn’t look to be 0.18.0 (.1 is supposed to not have issues anymore iirc, that’s why I’m specifying .0).

      This command was brought up in regards to the lemmy.ml issue:
      curl -I --user-agent "kbinBot v0.1" https://lemmy.ml/u/test

      When the lemmy.ml is replaced with any instance running 0.18.0, it’ll give an OK response. With lemmy.ml it gives a Forbidden response.

      But with lemdro.id I get an Internal Server Error.

      The instance claims to be super fast, maybe they forked and optimized the code and broke federation in the process?

      Edit: Also they’re on 0.18.1 anyway, so yeah, it’s not the usual issues.

      • Skull giver@popplesburger.hilciferous.nl
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        It looks like you’re right, lemmy.ml is blocking kBin.

        That has nothing to do with Lemmy versions, though. The source code and the standard web server configuration does no explicit blocking of kBin. Even if they update to Lemmy 0.19 or 0.20 the type of blocking they’re implementing probably won’t be lifted.

        Lemmy 0.18.1 isn’t out yet, so it could theoretically be a development release being broken, but I highly doubt it. I think the admins just block kbin for some reason.