68
I believe it's a bug in Lemmy itself that will be rectified in the next release. For now, like you say, just use 'New'.
Or top day
Top day is definitely the best right now
Also "new comments"
It does seem to be affecting this instance more though.
Just a heads up, it looks like there's an incredible uptick in development contribution to Lemmy and jerboa for Lemmy, so the next updates might not be far afield and specifically for jerboa the next version seems to fix a wide range of different bugs that people have been vocal about.
Ask your instance admin to restart the instance. It's a known bug. I've set our instance to restart every 4 hours since it takes about 20 seconds to do a restart and is way better than having a stale timeline. That said, SIJW has thousands of users while we only have 200. We can get by restarting, maybe with more users there will be more of a negative impact even if it's only for 20 seconds every 4 hours.
It is starting to look like it has something to do with out instance at this point.
It's the version of code we are running. Use 'new' until the dude can update our code.
Well, @TheDude@sh.itjust.works just gave it a test restart and it seems to have helped for now at least.
Sorting by top help shows better posts, hope that helps.
I switched to Top- Day, which helps. Still some stale stuff, so I switch to subscribed plus new every once in a while.
I asked and @TheDude@sh.itjust.works gave it a try. Looks like it's helping but idk if will need repeating.
I'm seeing 9 days old, it's really stuck.
There is an open bug about internal crashes within lemmy_server: https://github.com/LemmyNet/lemmy/issues/3076
A restart of the lemmy_server service might get it fixed for one-time.
view more: next ›
this post was submitted on 20 Jun 2023
68 points (100.0% liked)
sh.itjust.works Main Community
7584 readers
1 users here now
Home of the sh.itjust.works instance.
founded 1 year ago
MODERATORS