this post was submitted on 22 Jun 2023
10 points (100.0% liked)

Asklemmy

43916 readers
1484 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] GreyCat@lemmy.world 9 points 1 year ago (6 children)

From the Docs link available at the bottom right of any lemmy page, in "4. Votes and Ranking" :

  • Active (default): Calculates a rank based on the score and time of the latest comment, with decay over time
  • Hot: Like active, but uses time when the post was published
[–] soupspoon@lemmy.world 6 points 1 year ago (4 children)

Which means that active doesn't refresh to different posts as quickly

[–] Scooter411@lemmy.ml 3 points 1 year ago (1 children)

Both active and hot show me posts from 2 days ago… I have to sort by new to browse anything remotely up to date. I think they need to adjust their algorithm.

[–] King@vlemmy.net 4 points 1 year ago (1 children)

I remember reading an issue where the scheduled task to update hot and active was breaking shortly after reboot. So those lists were getting frozen in time, until the next reboot.

[–] Spitfire@pawb.social 2 points 1 year ago

Correct, it’s currently a bug in Lemmy. Your local instance/server will need to be restarted periodically to keep active and hot updating until it’s fixed.

load more comments (2 replies)
load more comments (3 replies)