Settings

What you can change, and where the rest lives

Displaystored in this browser

Source previewsThe card each source publishes — GitHub's repo card, Hugging Face's model thumbnail, a paper's first page. Off makes every list denser and stops the browser fetching around a thousand images per screen.

Trend scoresrc/lib/scoring/config.ts — every weight in the product lives there

velocity40%

momentum30%

freshness15%

quality15%

Relevance is deliberately not in this list. A score answering “is this moving” must not be partly “do we care”, or the radar can never tell us something irrelevant is exploding. It became the Fit score instead.

Opportunity scorecan we do something with it

trend30%

fit30%

headroom20%

accessibility10%

actionability10%

Confidence scorehow much this reading can bear

corroboration35%

measurement30%

depth20%

classification15%

Thresholdsthe numbers that decide what a status means

“Only interesting for us” keeps fit ≥ this

45d

Emerging: no older than

Emerging: at least this per day

×1.6

Emerging: accelerating at least

×1.15

Rising above

×0.7

Declining below

These are not editable here, and that is the honest position: they change what every stored snapshot means, so they belong in a commit somebody can review and revert.

Do the thresholds hold up?160h between the two runs compared

emerging7125%

rising3811%

stable66130%

emerging — 27 gone, 16 rising, 15 stable, 11 declining, 2 emerging
rising — 23 gone, 9 stable, 4 rising, 2 declining
stable — 427 gone, 133 stable, 60 rising, 38 declining, 3 emerging

27 runs carry a status, which is enough to read this seriously. The percentage is the share that held its ground — emerging that is still emerging or has become rising. 293 items appear in both runs, and the median trend score moved -2.0. Items the later run never saw are counted as “gone” rather than as a failed prediction — falling out of a search window is not evidence about a threshold.

Collectionwhat runs, how often, and what it looks for

17 */6 * * *

Schedule — four runs a day

Live sources

Page revalidation

The cadence lives in .github/workflows/snapshot.yml; four runs a day is a deliberate trade between resolution in time and the size of the repository, since the history is committed to it. What the radar searches for is a data file — the Topics screen shows it, what each direction returned, and how much of GitHub's request budget is spent.

This browsereverything personal lives here and nowhere else

Recommendations acted on

A colleague opening the same page sees none of this, and it does not follow you to another device. Sharing it needs a store the server can read, which is the one thing here that genuinely needs a database.