Skip to content
Signalcrest
Back to feed
devtoweb

HTTP gets a QUERY method so complex searches can stop pretending to be POST https://www.theregister.com/devops/2026/07/13/http-gets-a-query-method-so-complex-searches-can-stop-pretending-to-be-post/5270192

HTTP query method

Steady
Signal score
7
as of 56d ago
Trajectory
Too early
needs a few more snapshots

Why this scored 7

every term, weighted
Velocity+0.4 / 40

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

Acceleration+0.0 / 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+7.9 / 10

Decays to zero over 14 days

Saturation penalty1.1 / 30

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

Composite7.2

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

Signal history

7-day window (free)
Not enough history yet — the trend line fills in as snapshots accrue (every 30 min).

Entities

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

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