Signalcrest
← Back to feed
devtodata

I Tried Redis. It Didn't Fix Stateful MCP on ECS Fargate

Redis fails to fix state issue

Steady

13

signal score

🔗 3

sources · redis

↓ Cooling

7-day est. ~8

ShareLinkedInOpen source ↗

Why this scored 13

every term, weighted
Velocity+0.3 / 40 max

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

Acceleration+0.0 / 25 max

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

Cross-source spread+5.6 / 25 max

How many independent communities are talking about the same entity

Recency+7.8 / 10 max

Decays to zero over 14 days

Saturation penalty−1.2 / 30 max

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

Composite12.6

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

Outlook

low confidence · estimate, not a guarantee

7-day

~8

range 7–8

14-day

~6

range 6–7

30-day

~6

range 5–6

Signal history

7-day window (free)

— — projected trajectory (estimate, not a guarantee)

Entities

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

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