Sort by active broken on this instance?
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 replies
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
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.
That's good to know
I sort by “New” if I want the most recent
I sort by old if I want the oldest
In another thread someone mentioned sorting by Top-Day to get a better lost until the bug fix. It works for me.
I feel this a bit too. Maybe I'm just comparing it to kbin.
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.
Well @[email protected] just manually refreshed at least. Hopefully the bug gets fixed soon.
Hoping with ya! 🤞🔥
I have the same on my own instance too, my guess it's a bug in lemmy.
It is. Version 0.18 fixes it. Someday.