lean
for lean devs
Steady2
signal score
1
live items
↓ Cooling
7-day est. ~0
Why this scored 2
every term, weightedEngagement per hour, normalized against the fastest item on its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities are talking about the same entity
Decays to zero over 14 days
Subtracted once something is big and old — we rank what's next, not what's peaked
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 guarantee7-day
~0
range 0–1
14-day
~0
range 0–0
30-day
~0
range 0–0
Signal history
7-day window (free)— — projected trajectory (estimate, not a guarantee)
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.
- 116
A Rust-to-Lean verification pipeline with AI provers: An experience report
lobstersSteady20d ago - 213
Fast DEFLATE compression in Lean
Fast DEFLATE in Lean — for lean devs
lobstersdevtoolsSteady1d ago - 312
Introduction to Formal Verification with Lean (Part 1)
Improves code verification — for devtools founders
lobstersscienceSteady8d ago - 47
Introduction to Formal Verification with Lean Part 1
Formal verification introduced — for researchers, students
hackernewsscienceEmerging5d ago