Hi, seems like a change to authorisation has broken backwards compatibility. Avelon isn’t able to login to instances running 0.19 which is “just around the corner” according to Lemmy devs.

  • willya@lemmyf.uk
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    edit-2
    1 year ago

    They specifically say 4 weeks (more likely later) in their post…… some of the several instances running 0.19 grabbed it accidentally for the most part as they had there docker tag set to :latest and it grabs the nightly builds.

    • Phil K@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      I don’t get your point. We know it’s coming (whether it’s just around the corner or a month away), so it would be best to get ready to ensure compatibility. Especially when several instances are now no longer compatible with Avelon and other apps.

      Are you saying there’s no need to do anything ? Or something else?

      • willya@lemmyf.uk
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        1 year ago

        I was simply correcting some of the stuff you are typing out. Of course this stuff needs to be addressed.

        • Phil K@lemmy.worldOP
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          1 year ago

          ?? I literally just typed that Avelon won’t log into v0.19 which is factually true. I don’t understand why you replied that the update wasn’t happening for a month +?