devtoolsentity · one source so far

gcp

for devops engineers, product designers

Coolingdevto

Signal score

as of 32d ago

Live items

Trajectory

⏳ Too early

needs a few more snapshots

Why this scored 0

every term, weighted

Velocity+0.0 / 40

Its fastest-moving item, measured against the pace of its own source

Acceleration+0.0 / 25

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+0.0 / 25

How many independent communities its own items come from

Recency+0.0 / 10

Decays to zero over 14 days, counted from when we first saw it

Saturation penalty−4.2 / 30

Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it

Composite-4.2 → clamped to 0

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology

Signal history

7-day window (free)

Not enough history yet — the trend line fills in as snapshots accrue (every 30 min).

The evidence

The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.