I usually view my Lemmy instance by “All-Hot” because that seems to have the most relevant unread content. I sometimes filter by “top hour or 6 hours”.
When I leave and come back to voyager the feed is filled with old, stale content on initial load. If I go back to communities and reload “all” I then get a refreshed feed.
Why doesn’t it default to the latest “hot” posts when I load it?
Yeah, this is an annoying bug. I first assumed it is because I switched to beta for the piefed integration. But it’s still present even after the latest update
Can confirm! I’ll try to fix next release
Edit: potential fix deploying to test build, I will release in a couple days assuming no regressions
I saw the fix mentioned in the changelog, but this is still happening to me. When I open the app my subscribed communities defaults to Active sort, after a refresh it properly sorts by New. I switched to the beta and no luck there either.
It’s not fixed in release yet, just beta.
Do you have remember community sort turned on or off?
Remember Community Sort is on.
And now I can’t replicate the issue in beta. Maybe I simply imagined it happening after updating?
🤔 Please let me know if it comes back! And you can double check the version you’re running in the about app page.
I’ll kick off a release for this fix rn.
Thanks for listening!!
For a week or so, I’ve had to go to hot then back to scaled on first load of the app. Didn’t used to be this way.
Yeh I have noticed something similar.
I have to refresh home/local/all when I visit them to get all new posts. Default sort is new for all of them (iirc)
Occasionally there is 1 new one at the top of the feed.
I thought I was dreaming.
Same here, for a month or so.
I’ve been having a similar issue, mentioned it earlier and the dev said it might be a old Lemmy glitch? Hopefully we can get it figured out!
