eff
for privacy engineers, compliance teams
Why this scored 0
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
EFF to Governor Newsom: Veto California's AB 1709
EFF urges California governor to veto a bill expanding surveillance and data collection. · for privacy engineers, policy teams
hackernewsSteadysecurity46d ago - 216
Court agrees with EFF: Utah's VPN law demands a technical impossibility
Utah VPN law may be unenforceable, affecting privacy-focused services. · for privacy engineers, compliance teams
hackernewsSteadysecurity15d ago - 316
EFF to Courts: Don't Rewrite Copyright over AI Hype
EFF urges courts to avoid new copyright rules that could hinder AI development. · for legal teams, AI founders
hackernewsSteadyai47d ago