Skip to content

fix(likes): start Trending on day one and stop publishing detection windows - #65

Merged
jamesconwaydev merged 3 commits into
mainfrom
fix-trending-baseline
Nov 6, 2026
Merged

jamesconwaydev merged 3 commits into
mainfrom
fix-trending-baseline

Conversation

@jamesconwaydev

Copy link
Copy Markdown
Collaborator

Trending was empty for the first week after launch: with no snapshot from exactly 7 days ago every delta was 0, and a new repo had no baseline for 7 days. The baseline is now the 7-day snapshot if present, else the oldest snapshot at least a day old (no snapshot that old means deltas stay 0). Entries missing from the baseline count from 0 Likes, so delta_7d equals their Likes; their rank_delta_7d stays 0.

The burst and drip issue text also no longer states the detection windows, counts or the account-age cutoff, since that told people how to tune around the checks. The aggregate issue lists repos only.

Part of the v0.1 launch.

…indows

delta_7d now falls back to the oldest snapshot at least a day old when
there is none from 7 days ago, and entries missing from the baseline
count from 0 Likes. Burst and drip issue text no longer states the
windows, counts or account-age cutoff.
Skip snapshot files with impossible or non-ASCII dates, fail closed when
the chosen snapshot cannot be read, and make list_dir keep files only.
Trending now needs delta_7d >= 5 and an entry listed for 7 days or
added by seed.
@jamesconwaydev
jamesconwaydev merged commit 5f75ff2 into main Nov 6, 2026
8 checks passed
@jamesconwaydev
jamesconwaydev deleted the fix-trending-baseline branch November 6, 2026 03:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant