zsh
for shell script developers, sysadmins
Why this scored 9
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity'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)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 118
Tracking down a Zsh history data loss bug
Fixing zsh history bug · for shell devs
lobstersSteadydevtools63d ago - 216
Tracking down a Zsh history data loss bug
A bug can erase Zsh command history, affecting reproducibility of shell sessions. · for shell developers, sysadmins
hackernewsSteadydevtools56d ago - 315
Using a variable as a zsh modifier within a search pattern
Demonstrates using a variable as a Zsh modifier in search patterns for scripting. · for shell script developers, sysadmins
stackoverflowSteadydevtools32d ago