Is it just me, or is sort by active worse on sh.itjust.works than on other instances? On sh.itjust.works, it gives posts (both local and federated) that are weeks old. If I do the same on lemmy.world, it gives much more relevant posts that are a few hours to around a day old. Maybe there are some server settings that could be tweaked?
13 Comments
lemmy@acqrs.co.uk · 11 pts · 3y
This is a current bug that will be fixed in the next version I believe. Some instances periodically restart the instance to get this statistic repopulated
Seraph089@sh.itjust.works · 4 pts · 3y
And to make matters annoying, restarting the service that causes the sorting bug can trigger some other bugs (federation errors iirc). So there isn't a "right" answer until the real fix comes.
Gentoo1337@sh.itjust.works · 2 pts · 3y
That's good to know
timmytbt@sh.itjust.works · 8 pts · 3y
I sort by “New” if I want the most recent
god@sh.itjust.works · 2 pts · 3y
I sort by old if I want the oldest
TheDailyChase@sh.itjust.works · 6 pts · 3y
In another thread someone mentioned sorting by Top-Day to get a better lost until the bug fix. It works for me.
can@sh.itjust.works · 5 pts · 3y
I feel this a bit too. Maybe I'm just comparing it to kbin.
god@sh.itjust.works · 2 pts · 3y
It is broken in software. It's a bug that kills the refresher for the database, so the active posts simply don't get updated at all. Update coming someday.
can@sh.itjust.works · 3 pts · 3y
Well @TheDude@sh.itjust.works just manually refreshed at least. Hopefully the bug gets fixed soon.
god@sh.itjust.works · 3 pts · 3y
Hoping with ya! 🤞🔥
jeena@jemmy.jeena.net · 2 pts · 3y
I have the same on my own instance too, my guess it's a bug in lemmy.
god@sh.itjust.works · 2 pts · 3y
It is. Version 0.18 fixes it. Someday.