Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Scaled sort only shows posts created in last hour #4608

Open
5 tasks done
Nutomic opened this issue Apr 8, 2024 · 4 comments
Open
5 tasks done

[Bug]: Scaled sort only shows posts created in last hour #4608

Nutomic opened this issue Apr 8, 2024 · 4 comments
Labels
area: database bug Something isn't working

Comments

@Nutomic
Copy link
Member

Nutomic commented Apr 8, 2024

Requirements

  • Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • Did you check to see if this issue already exists?
  • Is this only a single bug? Do not put multiple bugs in one issue.
  • Do you agree to follow the rules in our Code of Conduct?
  • Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Summary

Effectively it works as another "new" sort, instead of fulfilling the stated goal of showing popular posts from smaller communities. It seems the algorithm needs some adjustment.

See https://lemmy.ml/?dataType=Post&listingType=All&sort=Scaled

cc @dessalines @dullbananas

Version

0.19.3

@Nutomic Nutomic added bug Something isn't working area: database labels Apr 8, 2024
@dullbananas
Copy link
Collaborator

The scheduled task to update scaled ranks should also be looled at

@dessalines
Copy link
Member

I think its working as intended, bc when I change the filter to Local, it did find many posts older than an hour.

You're not going to see many older posts with Scaled + All, because there's so many small communities with new posts that its giving a boost to.

@Die4Ever
Copy link

I do think Scaled is pretty good for the Subscribed feed, I use that as my default. Although I do think it could favor new posts a little less, and maybe Hot could use the same tweak

Somewhat related issue #4471

@dullbananas
Copy link
Collaborator

There's a small chance that this happens because the batches for updating the ranks use published instead of id, and a newly inserted post is only guaranteed to be the most recently published post if it's local.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: database bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants