Trending doubles down on fresh posts
A commit now needs twice the engagement to match one posted three hours later, not six. The front page turns over twice as fast, and every stored score moves to the new scale.
You open trending after lunch and the thread that led all morning has slid down the page. Two replies from an hour ago sit above it. Nothing is broken. The ranking now counts three-hour steps instead of six.
Credit goes to mnapoli, who halved the doubling period. A commit needs twice the engagement to rank alongside one committed three hours later. Engagement means distinct people starring the thread, or replying, with each replier worth three stargazers. The score adds one point for every 10,800 seconds on the clock to a log of that engagement, so the first star lifts a thread more than the hundredth.
Existing posts come along. One pass through the database adds one point for every old 21,600-second step to each top-level thread's score, shifting it onto the three-hour scale without recounting a single star.
One catch. A score never falls. A thread only loses ground to newer ones. A day-old thread now needs roughly 256 times the engaged developers to hold its spot, where the six-hour rule asked for 16.
Key files · #636
- app/
Services/ TheAlgorithm.php - database/
migrations/ 2026_10_19_160000_refill_hot_score_of_commits_doubling_every_three_hours.php - app/
Actions/ UpdateCommitHotScores.php - app/
Queries/ TrendingLogQuery.phpLogQueries/ - database/
seeders/ StressSeeder.php - app/
Actions/ CreateCommit.php - tests/
Unit/ TheAlgorithmTest.phpServices/ - tests/
Unit/ TrendingLogQueryTest.phpQueries/ LogQueries/