Signalcrest
← Back to feed
devtodevtools

I Found Two Bugs in Zulip. The Maintainers Had Filed Both Two Weeks Earlier.

Bug tracking

Steady

31

signal score

🔗 2

sources · python

Cooling

7-day est. ~19

Why this scored 31

every term, weighted
Velocity+0.0 / 40 max

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+10.8 / 25 max

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

Cross-source spread+12.5 / 25 max

How many independent communities are talking about the same entity

Recency+8.5 / 10 max

Decays to zero over 14 days

Saturation penalty1.0 / 30 max

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

Composite30.8

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, 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

~19

range 929

14-day

~16

range 428

30-day

~15

range 031

Signal history

7-day window (free)

— — projected trajectory (estimate, not a guarantee)

Entities

zulippython
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/dev%3A4225297)](https://www.signalcrest.app/topic/dev%3A4225297)

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