We’ve upgraded lemmy.world to 0.18.1-rc.1 and rolled back that upgrade because of issues.

(If you had posted anything in those 10 minutes between upgrade and rollback, that post is gone. Sorry!)

The main issue we saw is that users can’t login anymore. Existing sessions still worked, but new logins failed (from macos, ios and android. From linux and windows it worked)

Also new account creation didn’t work.

I’ll create an issue for the devs and retry once it’s fixed.

Edit Contacted the devs, they tell me to try again with lemmy-ui at version 0.18.0. Will try again, brace for some downtime!

Edit 2 So we upgraded again, and it seemed to work nicely! But then it slowed down so much it was unuseable. There were many locks in the database. People reported many JSON errors. Sorry, we won’t be on 0.18.1 any time soon I’m afraid…

  • axzxc1236@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    2 years ago

    Reasons I can think of:

    1. The official Android client for lemmy, Jerboa, only supports 0.18 and later, unless users download older version from github and sideload manually.

    2. Sorting is broken pre 0.18, new posts keeps flowing in.

    3. Performance improvement by removing web socket from lemmy. (which fixes 2, which is why 1. happens)

    • JdW@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      2 years ago

      Jerboa works fine with lemmy world, it just gives a warning and crashes on occasion. Not an issue to use it though.

      • Disk@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Yes, if you are already logged in. If you are not logged in, or get logged out you will not be able to log back in until the server version is above 0.18

      • inverimus@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        As a new user I tried logging in on Jerboa and it says the server must be on 0.18 and refuses the login.

      • Vanon@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        “crashes on occasion”

        Unfortunately, the occasion seems to be at least once every five minutes for me. thisisfine.jpg This is not fine and definitely a major issue. Especially as we get closer to July 1. After this news from lemmy.world, I will have to switch, probably to Connect, until Sync arrives.

      • Guy_Fieris_Hair@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        With the last couple updates jerboa has got to a point that I probably won’t even move to sync when it comes. I’m pretty happy with it. But if Lemmy Is Fun ever happens, I’m out.

        • grue@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I’m of a similar mind: I’m happy with Jerboa, yet also looking forward to Slide.

      • Cadenza@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Well you’re a lucky one. Jerboa has been unusable for me and other folks post v0.34 since the first rc release of 0.18. I finally managed to downgrade to 0.34 and login after lots of black magic. It used to crash instantly, even on 0.34.

        That being said, good luck to lemmy.world admins and thanks a lot for the open comms !

      • flawedFraction@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 years ago

        For me at least, I’m unable to change the community scope or sorting method. The only thing I can use Jerboa for is “local” and sorted by “active”. It isn’t totally unusable, but I would much rather be able to switch to subscribed and hot.

          • flawedFraction@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            Unfortunately that didn’t work for me. Thanks for the idea, though. I’m sure it will work for some. I suspect that if I wiped the app and set everything back up it might work, but that’s more than I’m willing to do at the moment and I can live with the inconvenience for now.

    • WhiskyTangoFoxtrot@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      The official Android client for lemmy, Jerboa, only supports 0.18 and later, unless users download older version from github and sideload manually.

      Even that won’t work, because Jerboa initially tries to connect to lemmy.ml which is running 0.18, which older versions of Jerboa aren’t compatible with. The app just crashes instantly without giving you the opportunity to log in to your instance.

      • KrapKake@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I don’t know but I installed and older version of Jerboa from F-Droid store. I couldn’t login from the most recent version of Jerboa because of this so it was pretty much useless for me. Working fine so far.

      • average650@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        The latest version only supports 0.18 because the backend works differently. Older versions of Jerboa support older backends of lemmy.

      • astanix@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Likely because Jebora is written as a side project of the devs of lemmy so it’s always going to be cutting edge

        • Graphine@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I understand that. I’m not complaining about the quality. I’m just confused from a technical perspective why it doesn’t support rollback or older server versions in the event of…this.

          • Darorad@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Fixing the issues with posts appearing and scrolling the page the backend needed some pretty drastic rewrites. I’m not super familiar, but from what I’ve seen of the code, it would be a decent amount more work to support both versions.

            Would it have been worth it? Yes, but it wasn’t anticipated that devs would stay on 0.0.17 for more than a day or two. With the time it takes for app stores to update, servers would have been updated before lemmy 0.0.45 was updated for the vast majority of users. At most, it would be a day or two instead of a week or two.