devtodevtools

I Fixed a Bug That Lived in FFmpeg for 8 Years.

8-year bug fixed in FFmpeg

Steady

signal score

🔗 2

sources · ffmpeg

→ Steady

7-day est. ~13

Share LinkedIn Open source ↗

Why this scored 10

every term, weighted

Velocity+0.9 / 40 max

Engagement per hour, normalized against the fastest item on its own source

Acceleration+0.0 / 25 max

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

Cross-source spread+2.8 / 25 max

How many independent communities are talking about the same entity

Recency+7.9 / 10 max

Decays to zero over 14 days

Saturation penalty−1.1 / 30 max

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite10.4

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement. Full methodology

Outlook

low confidence · estimate, not a guarantee

7-day

~13

range 11–14

14-day

~13

range 11–15

30-day

~14

range 11–16

Signal history

7-day window (free)

— — projected trajectory (estimate, not a guarantee)

Entities

ffmpeg

Embed a live signal badge

[![Signalcrest signal](https://www.signalcrest.app/api/badge/dev%3A4181465)](https://www.signalcrest.app/topic/dev%3A4181465)

Drop this in a README or blog post — it updates automatically as the score moves.