telegram — cross-source trend

Back to entity feed

devtoolsentity · one source so far

for backend engineers, devops

Steadygithub

Signal score

as of 4d ago

Live items

Trajectory

→ Steady

7-day est. ~0

Why this scored 0

every term, weighted

Velocity+0.0 / 40

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

Acceleration+12.2 / 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−17.9 / 30

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

Composite-5.7 → 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

Outlook

low confidence · estimate, not a guarantee

7-day

range 0–12

14-day

range 0–14

30-day

range 0–19

Signal history

7-day window (free)

projected trajectory (estimate, not a guarantee)

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.