this post was submitted on 14 Jan 2024
12 points (83.3% liked)

Quark's

1097 readers
1 users here now

Come to Quark’s, Quark’s is Fun!

General off-topic chat for the crew of startrek.website. Trek-adjacent discussions, other sci-fi television, navigating the Fediverse, server meta (within reason), selling expired cases of Yamok sauce, it’s all fair game.

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
12
StarTrek.website has updated to Lemmy version 0.19.3 (Clear cache/cookies in browser or remove+re-add account in app if experiencing login issues) (startrek.website)
submitted 10 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
10 comments fedilink hide all child comments
 

We had been waiting at 0.18.5 for a while because 0.19 came with some federation bugs (and obviously it would be extremely embarrassing if this instance had issues in that department).

The biggest changes for users are a new scaled sorting method that should prioritize posts from smaller communities (no more Risa dominating the entire feed), the ability for users to block whole instances, and the ability to import/export accounts with other instances (or just back up your account).

Also I'd like to apologize for the downtime; we expected this to be a simple update taking only a few minutes, so I didn't post an alert in advance, but then were some issues that caused us to go offline for several hours.

Lastly, after the update I found I had to clear my browser cache/cookies in order to log in, similarly, users using apps have been reporting they needed to remove and re-add their accounts. You may find you need to do that too!

EDIT: The app Liftoff has a bug preventing login on any Lemmy instance over v0.19.0

Drunk

EDIT 2: We've updated to 0.19.3, mostly just bugfixes in this one.

all 46 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 9 months ago (1 children)

I have not been able to log in at all, even after trying multiple browsers, until today! Glad to be back

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

Why are lemmy updates so weird and disruptive?

I had to clear all my website data to log in via the website, which I've never ever seen any other website require.

The app situation was not much better, I needed to remove all my accounts on Boost and totally reinstall Mlem.

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

Same here. Had to purge everything, as all I would get was site errors.

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

In Mlem you need to confirm your account before deleting it from the app, so I actually had to delete the whole app

Works now though.

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

Glad to see this as I did all the above and it’s still not working in Mlem. I’ll give this a try though.

[–] [email protected] 0 points 10 months ago

Yeah try deleting the app, check your phones storage in settings > general > storage and search for Mlem. If you delete it it will remove all data from your phone, then you can reinstall and sign in again.

[–] [email protected] 0 points 10 months ago

Hopefully people who browse lemmy via browser are finding a way to read this page. This post was failing to load for me even while logged out for some reason. Luckily I saw it from a mobile app and knew to clear cache/cookies, because otherwise I might have just assumed it was down.

[–] [email protected] -1 points 10 months ago

Nice! I have been waiting for this, eagerly anticipating when I can block the entire hexbear instance (I made the mistake of commenting in one of their magazines once and despite how many days ago that was the sheer flood and content of the responses continues to be... let's just say enlightening in terms of how they choose to exist). So this is fantastic! :-P

[–] [email protected] 0 points 10 months ago

Ummm yeah, I'm going to need to to submit a change request before all maintenance. The change management board will need to approve it before you can do anything.

Jk, thanks for all you do. After logging out and back in on sync, I'm back up.