Skip to content
Signalcrest
Back to feed
lobstersdevtools

Why Emacs Consult async searches feel slow and how to speed them up

Explains why Emacs Consult async searches feel slow and how to speed them up.

Steady
Signal score
18
as of 1d ago
Trajectory
Cooling
7-day est. ~0

Why this scored 18

every term, weighted
Velocity+0.0 / 40

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

Acceleration+9.3 / 25

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

Cross-source spread+0.0 / 25

How many independent communities are talking about the same entity

Recency+9.2 / 10

Decays to zero over 14 days

Saturation penalty0.6 / 30

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

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

~0

range 012

14-day

~0

range 014

30-day

~0

range 019

Signal history

7-day window (free)
062

projected trajectory (estimate, not a guarantee)

Entities

emacs consult
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/lob%3Affvipw)](https://www.signalcrest.app/topic/lob%3Affvipw)

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