Signalcrest
← Back to feed
hackernewsdevtools

Why we write our own C and C++ inference engines

Custom inference engines

Emerging

14

signal score

as of 2d ago

🔗 3

sources · c

Too early

trajectory — needs a few more snapshots

Why this scored 14

every term, weighted
Velocity+0.4 / 40 max

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

Acceleration+2.1 / 25 max

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

Cross-source spread+6.3 / 25 max

How many independent communities are talking about the same entity

Recency+7.9 / 10 max

Decays to zero over 14 days

Saturation penalty2.7 / 30 max

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

Composite13.9

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

Signal history

7-day window (free)

Entities

cc++
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/hn%3A49125065)](https://www.signalcrest.app/topic/hn%3A49125065)

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