I'll be restarting AZ today for an update to lemmy 0.19.

Upgrade complete.

This is a major upgrade, so I expect there to be some issues. Strap in, enjoy the ride.

Expect:

  • further restarts
  • bugs
  • slowdowns
  • logouts
  • 2FA being disabled
  • possibly issues with images, upgrading pictrs to 0.4 at the same time
  • hitmyspot@aussie.zone
    ·
    7 months ago

    Just a heads up that liftoff no longer works as it has not had necessary upgrades to be co patibke with 0.19

    It is now end of life unless the dev returns. There have been no updates for a few months.

    • Nath@aussie.zone
      ·
      7 months ago

      I use Boost in compact mode. I selected it because it felt like BaconReader. Also, it was only $5ish.

    • veroxii@aussie.zone
      ·
      7 months ago

      Thanks. I really liked liftoff... Was the closest to baconreader from the olden days.

      Posting this reply on summit. Really good and very similar to liftoff so far (at least in dark mode)

    • Lodion 🇦🇺@aussie.zoneM
      ·
      7 months ago

      Lots of back end improvements... on the user facing side 2FA enrollment improvements, and highlighting of recent comments. I've not noticed anything else, but I'm sure its there.

      • Baku@aussie.zone
        ·
        7 months ago

        I'm happy about the new 2fa system! The old one was so confusing I gave up even trying. One thing I did have a question about: are there backup codes somewhere I can download in case I lose my app or whatever?

  • legios@aussie.zone
    ·
    7 months ago

    Hey hey - with Jerboa on Android I'm getting "failed to verify JWT token". Looked it up an it appears to be an issue with Jerboa (https://github.com/dessalines/jerboa/issues/1285) so no action needed on your side, just an FYI for people here I guess!

      • Baku@aussie.zone
        ·
        7 months ago

        My TPA (Boost) seems to no longer be showing karma amounts on user profiles. The update has broken whatever method boost used to extract that number, I presume?

        *removed externally hosted image*

        • Nath@aussie.zone
          ·
          7 months ago

          I think I'm ok with this. I liked the initial concept of karma not being tracked long-term.

          I won't really mind if the apps bring this data back, but I won't lose sleep if it's gone.

          • Baku@aussie.zone
            ·
            6 months ago

            I don't know, I kind of like having imaginary internet points, but maybe having it as an off by default toggle might be a good middle ground

      • maniacalmanicmania@aussie.zone
        ·
        7 months ago

        2-factor authentication is no longer enabled as it was before the upgrade. I'm not sure if the 2FA code option on the enabling modal is part of setting up new authentication or for using old auth code and I haven't tested it.

        • Lodion 🇦🇺@aussie.zoneM
          ·
          7 months ago

          This was deliberate on the part of the devs. Old 2FA enrollment was finicky and error prone, locking many users out. So they've disabled it for everyone, forcing re-enrollment to enable it.

            • Lodion 🇦🇺@aussie.zoneM
              ·
              7 months ago

              You've got a good memory. Yes, the new process is slightly different so the old guide isn't relevant. Also its not as important anyway, enrolling no longer enables 2FA before you have a device capable of generating TOTP codes.

              • maniacalmanicmania@aussie.zone
                ·
                7 months ago

                I see. I didn't really understand the complication last time but appreciated the guide. Re-enrolling was a cinch. I best do the bot account. Anything about bot accounts we should know about after this upgrade?

                  • maniacalmanicmania@aussie.zone
                    ·
                    7 months ago

                    Done. I don't know if this counts as an issue but on Chrome after setting up 2FA, logging out and logging in to test if the 2FA prompt came up there was briefly a little red error pop up on the bottom left of the browser that said 'Error: mising_totp_token'. Seems like something that should only come up after submitting a blank value not when the 2FA popup first appears. Probably something for the lemmy devs but sharing with you in case it's config or other. No other issues to report so far. Thanks again.

                      • maniacalmanicmania@aussie.zone
                        ·
                        7 months ago

                        There is a similar Error message issue for anonymous users (at least on desktop Firefox). The message is 'Error: incorrect_login'. If it happened once per session I wouldn't bring it up but I noticed that it happens for every page visit and sometimes while scrolling through comments, even after it has already popped up on the same page. Dunno if anonymous user traffic/experience warrants any concern though. Cheers.

      • maniacalmanicmania@aussie.zone
        ·
        7 months ago

        OK. I might make add each issue as a separate comment. Let me know if you prefer they are combined.

        1. I get this when I try to access my profile *removed externally hosted image*
  • Aesecakes@aussie.zone
    ·
    6 months ago

    Will broken images come back at some point?

    Getting this message on some, but not all images:

    {"msg":"Socket not connected (os error 107)"}

  • Gbagginsthe3rd@aussie.zone
    ·
    7 months ago

    Error with Memmy on iOS. Needed to log out and log back in.

    Apparently there was an issue with my password being incorrect. However I hadn’t changed anything.

    • Baku@aussie.zone
      ·
      7 months ago

      The log in errors and needing to re log in is a standard thing AFAICT. I was in a weird unauthenticated but still logged in state on boost and had to log back in on desktop too