this post was submitted on 20 Jun 2023
45 points (100.0% liked)

General Discussion

250 readers
1 users here now

Want something to discuss? Post it here

Follow instance rules, be decent human being...

founded 1 year ago
MODERATORS
 

My “hot” and “active” page have been showing the same posts for four days. I only get new content if I sort by “Top of Today” or “New”. I’m subscribed to plenty of communities.

Anyone else have this issue or know what the problem is?

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

Its a bug in this Version of Lemmy (0.17.x). It will be fixed in the next Version (0.18).

[–] [email protected] 3 points 1 year ago

Thanks, good to know!

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

I have this too, made worse in Jerboa where it won't even remember my filter settings so I have to go to All and New every time to see anything.

Edit: oops, found you could change the defaults in Jerboa settings. Still shouldn't need to, it should just remember last choice, but at least it's possible.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Someone raised an issue on github asking for ability to set default setting for each subscribed, local and all tabs. Not sure how it went.

Edit: found the github issue: https://github.com/LemmyNet/lemmy-ui/issues/1359

[–] [email protected] 5 points 1 year ago (1 children)

Yup, same with me. I was trying to look at what's going on and I wind up getting engaged with New a lot too.

Not sure what the problem is or how it's remedied....

[–] [email protected] 1 points 1 year ago

It's a known issue, the next version of Lemmy fixes it and it should be out soon for instance owners to upgrade to.

[–] [email protected] 2 points 1 year ago

Restarting the instance on 17.x either fixes it temporarily or just refreshes it once. Some people have been calling to just restart the server once a day

[–] derf82 1 points 1 year ago

There was a bug in the software. Some instances have fixed it, others have not.

load more comments
view more: next ›