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?

11 points

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

permalink
report
reply
4 points

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.

permalink
report
parent
reply
2 points

That’s good to know

permalink
report
parent
reply
8 points

I sort by “New” if I want the most recent

permalink
report
reply
2 points

I sort by old if I want the oldest

permalink
report
parent
reply
6 points

In another thread someone mentioned sorting by Top-Day to get a better lost until the bug fix. It works for me.

permalink
report
reply
5 points

I feel this a bit too. Maybe I’m just comparing it to kbin.

permalink
report
reply
2 points

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.

permalink
report
parent
reply
3 points
*

Well @TheDude@sh.itjust.works just manually refreshed at least. Hopefully the bug gets fixed soon.

permalink
report
parent
reply
3 points

Hoping with ya! 🤞🔥

permalink
report
parent
reply
2 points

I have the same on my own instance too, my guess it’s a bug in lemmy.

permalink
report
reply
2 points

It is. Version 0.18 fixes it. Someday.

permalink
report
parent
reply

sh.itjust.works Main Community

!main@sh.itjust.works

Create post

Home of the sh.itjust.works instance.

Community stats

  • 963

    Monthly active users

  • 432

    Posts

  • 11K

    Comments