Skip to content
Signalcrest
Back to feed
devtodevtools

What Protobuf descriptors don't tell you: building a generic mock generator

Shows how to build a generic mock generator from protobuf descriptors for testing.

Steady
Signal score
31
Sources
2
agreeing on protobuf
Trajectory
→ Steady
7-day est. ~24

Why this scored 31

every term, weighted
Velocity+0.0 / 40

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

Acceleration+11.2 / 25

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

Cross-source spread+12.5 / 25

How many independent communities are talking about the same entity

Recency+8.2 / 10

Decays to zero over 14 days

Saturation penalty−0.3 / 30

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

Composite31.5

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

~24

range 0–36

14-day

~25

range 0–39

30-day

~25

range 0–44

Signal history

7-day window (free)
1632

projected trajectory (estimate, not a guarantee)

Entities

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

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