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.
Yea, poor Liftoff
Hope the dev is doing well with the twins.
Oh, twins. A different kind of liftoff for them.
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)
I use Boost in compact mode. I selected it because it felt like BaconReader. Also, it was only $5ish.
What new goodies does .19 come with?
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.
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?
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!
Thank you.
Is this where we should post issues if we have any?
Sure
What if it’s personal psychological issue?
You know what they say; it's best to unload all your emotional baggage onto strangers in a public forum.
LOL
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?
That would be my guess. There have been pretty major changes to the API as I understand it.
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.
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
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.
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.
I think you made a guide for enabling this properly but I cannot seem to find it. Would that guide be deprecated now?
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.
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?
I didn't see anything bot related from my skim of the change notes... should be fine.
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.
Noticed the same. Seems to be cosmetic so I'm ignoring it for now 🤷♂️
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.
OK. I might make add each issue as a separate comment. Let me know if you prefer they are combined.
Spotted this one myself, but its not isolated to a user's own profile. Suspect its a back end lemmy issue... will investigate.
Edit, nope... postgres docker memory issue... seems to be fixed after adding "shm_size: '1gb'" to the docker postgres compose stanza.
Seems to be fixed at my end also. Thank you.
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!
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.
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
Ahhhhh logouts... That explains what happened to me.
Thanks for your efforts!
Seems to be working sweet in Voyager, just the log out and we're away again.
Cheers computer expert guy!
I can't seem to log in to Jerboa. Guess it hasn't been updated with 0.19 support yet. Ah well.
Wait, I just needed to manually update Jerboa. It hadn't updated automatically for some reason.
Will broken images come back at some point?
Getting this message on some, but not all images:
{"msg":"Socket not connected (os error 107)"}
I've not seen that myself, will look into it tonight.
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.
pictrs seems to have given up, and is refusing to run... new thumbnails etc are not being created. I'm looking at it.
A quick server reboot and it seems to be back. Looked like my postgres config caused some memory issues, which killed off back end object storage... and pictrs barfed.
👍
The issue has returned …
Yeah, another reboot... have updated to lemmy 0.19.1 also. For some reason we're hitting memory exhaustion on the host now... never did before. I'll see what I can figure out.
I got something you can strap into ;)
Discussion about the aussie.zone instance itself
