Lemmy 0.19 Upgrade (aussie.zone)
submitted 2 years ago* (last edited 2 years ago) by [M] to c/meta@aussie.zone
 

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

all 48 comments

sorted by: hot top controversial new old
[–] 7 points 2 years ago (3 children)

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.

  • source
  • hideshow 6 child comments
  • [–] 1 point 2 years 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)

  • source
  • parent
  • [+] 6 points 2 years ago* (last edited 2 years ago) (1 child)
  • [–] [S] 7 points 2 years ago (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 years ago

    On the inbox page, if you tick the "mark as read" button, it now immediately gets rid of that comment. Which personally I actually view as a degradation.

    But also, on a post page, you can now interact with other elements in the middle of writing a comment, and it doesn't automatically cancel your comment. So now you can safely upvote the comment you're replying to half way through writing that reply! This is awesome!

  • source
  • parent
  • [–] 3 points 2 years ago
    [–] 2 points 2 years ago (1 child)

    Is this where we should post issues if we have any?

  • source
  • hideshow 2 child comments
  • [–] [S] 2 points 2 years ago (4 children)
  • [–] 6 points 2 years ago (1 child)

    What if it’s personal psychological issue?

  • source
  • parent
  • hideshow 2 child comments
  • [+] 3 points 2 years ago* (last edited 2 years ago) (2 children)
  • [–] 2 points 2 years ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 4 points 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    I think you made a guide for enabling this properly but I cannot seem to find it. Would that guide be deprecated now?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 2 years ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    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?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 2 years ago (1 child)

    I didn't see anything bot related from my skim of the change notes... should be fine.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 3 points 2 years ago (1 child)

    Noticed the same. Seems to be cosmetic so I'm ignoring it for now 🤷‍♂️

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years 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.

  • source
  • parent
  • [–] 1 point 2 years ago (1 child)

    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
  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 1 point 2 years ago (1 child)

    Spotted this one myself, but its not isolated to a user's own profile. Suspect its a back end lemmy issue... will investigate.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years 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!

  • source
  • [–] 1 point 2 years ago (1 child)

    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.

  • source
  • hideshow 2 child comments
  • [–] 1 point 2 years ago

    Ahhhhh logouts... That explains what happened to me.

    Thanks for your efforts!

  • source
  • [–] 1 point 2 years ago

    Seems to be working sweet in Voyager, just the log out and we're away again.

    Cheers computer expert guy!

  • source
  • [–] 1 point 2 years ago (1 child)

    I can't seem to log in to Jerboa. Guess it hasn't been updated with 0.19 support yet. Ah well.

  • source
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    Will broken images come back at some point?

    Getting this message on some, but not all images:

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

  • source
  • hideshow 2 child comments
  • [–] [S] 2 points 2 years ago (1 child)

    I've not seen that myself, will look into it tonight.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    Here is a screenshot. Couldn't upload it directly using both Vivaldi/Chrome or Firefox browsers on a Mac. Using Voyager, am getting (os error 107) when trying to add image to a post.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 1 point 2 years ago (2 children)

    pictrs seems to have given up, and is refusing to run... new thumbnails etc are not being created. I'm looking at it.

  • source
  • parent
  • hideshow 4 child comments
  • [–] -2 points 2 years ago

    I got something you can strap into ;)

  • source