sh.itjust.works Main Community

7729 readers

1 users here now

Home of the sh.itjust.works instance.

founded 1 year ago

MODERATORS

Sort by active broken on this instance? (self.main)

submitted 1 year ago by dack to c/main

12 comments fedilink hide all child comments

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?

top 12 comments

sorted by: hot top controversial new old

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

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 4 points 1 year ago

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 2 points 1 year ago

That's good to know

[–] timmytbt 8 points 1 year ago (1 children)

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

[–] god 2 points 1 year ago

I sort by old if I want the oldest

[–] TheDailyChase 6 points 1 year ago

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

[–] can 5 points 1 year ago (1 children)

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

[–] god 2 points 1 year ago (1 children)

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 3 points 1 year ago* (last edited 1 year ago) (1 children)

Well @[email protected] just manually refreshed at least. Hopefully the bug gets fixed soon.

[–] god 3 points 1 year ago

Hoping with ya! 🤞🔥

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

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

[–] god 2 points 1 year ago

It is. Version 0.18 fixes it. Someday.