This needs to be addressed by the devs in my opinion... I read that the way the Hot score is calculated needs to be changed either way since it's currently horrible for the performance.
this post was submitted on 09 Jun 2023
21 points (100.0% liked)
Beehaw Support
153 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our July 2023 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
I saw a post over on lemmy.ml as a request for comments on this..
Essentially apply a weighting to popularities based on community size.
I imagine an issue will pop up on the GitHub soon to centralise the discussion.
If it's horrible for performance, it should be bundled by cron jobs instead of recalculated every single request
It’s not that. You can read the issue detail but essentially the database query for hot sorting is currently inefficient.
I have noticed that when click "all" and "active", after a minute or two my page will load a random instance's entire list today.
Here is an example