this post was submitted on 17 Dec 2023
59 points (100.0% liked)

Meta

55 readers
3 users here now

Discussion about the aussie.zone instance itself

founded 1 year ago
MODERATORS
59
Lemmy 0.19 Upgrade (aussie.zone)
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 

~~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
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 11 months ago (1 children)

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

[–] [email protected] 2 points 11 months ago (4 children)
[–] [email protected] 6 points 11 months ago (1 children)

What if it’s personal psychological issue?

[–] [email protected] 4 points 11 months ago (1 children)

You know what they say; it's best to unload all your emotional baggage onto strangers in a public forum.

[–] [email protected] 3 points 11 months ago (2 children)

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?

[–] [email protected] 2 points 11 months ago

That would be my guess. There have been pretty major changes to the API as I understand it.

[–] [email protected] 1 points 11 months ago (1 children)

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.

[–] [email protected] 1 points 11 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

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 4 points 11 months ago (1 children)

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.

[–] [email protected] 2 points 11 months ago (1 children)

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

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 2 points 11 months ago (1 children)

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?

[–] [email protected] 2 points 11 months ago (1 children)

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

[–] [email protected] 2 points 11 months ago (1 children)

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.

[–] [email protected] 3 points 11 months ago (1 children)

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

[–] [email protected] 2 points 11 months ago* (last edited 11 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.

[–] [email protected] 1 points 11 months ago (1 children)

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
[–] [email protected] 1 points 11 months ago (1 children)

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

[–] [email protected] 1 points 11 months ago (1 children)

Edit, nope... postgres docker memory issue... seems to be fixed after adding "shm_size: '1gb'" to the docker postgres compose stanza.

[–] [email protected] 1 points 11 months ago

Seems to be fixed at my end also. Thank you.