Radar · live

What's moving through AI, ranked by lead time.

Radar is an hourly index of what's moving through the AI ecosystem, ranked by where each story sits on the lead-time gradient: papers become repos become community threads become analysis. The earlier a story is caught, the more head start you have before the crowd. Every row carries its receipts — which source saw it first, how many independent sources have it, how long ago — so the ranking explains itself. It's the public face of the same pipeline that feeds Vlad's Newsletter.

snapshot 11 Aug 2026, 19:28 UTC · 67/78 feeds live · 19,031 tracked since 12 Jun

Moving now see all 40 ↓
40 tracked · 4 heating · 11 feeds quiet · 0 of 4 stations quiet
  1. 1 Mojo 1.0 is here modular.com · 3h
  2. 2 Show HN: My Anti AI Computer punkx.org · 4h
  3. 3 Nvidia's Risky Business stratechery.com · 10h
  4. 4 Show HN: My LLM kept getting blocked, so I gave it a browser that looks human github.com · 12m
  5. 5 Show HN: Webstractor – Pay-as-You-Go Web Data API for AI Agents webstractor.com · 12m
Lead-time spectrum
flow, last 24h · 0 dark
369
Papers
4
Repos
269
Community
26
Analysis

668 stories entered the watched feeds in the last 24 hours — 369 in papers, 4 in repos, 269 in community, 26 in analysis. The scored board skews to Community (40 of 40). 4 stories are heating across independent sources, and the median lead across the ledger's 24 observed fires is 5h — measured, not estimated. Freshest receipt, 1h ago: caught in Hacker News front 4h before Stratechery carried it. The oldest survivor has held the board for 10h.

40
on the board
4
heating
40
new on board
5h
median lead
Latest fires — measured lead
  1. Community → Analysis +4h lead Hacker News front first · then Stratechery 1h ago
    Nvidia's Risky Business
  2. Repos → Community +35h lead GitHub Trending Python first · then Show HN 28h ago
    superlinked/sie
  3. Community → Analysis +2h lead Hacker News front first · then OpenAI News 4d ago
    Responding to the next frontier of critical cyber capabilities
  1. 1
    Mojo 1.0 is here
    modular.com
    Live Signal Community · 3h old · seen in 2 sources HEATING ×2
  2. 2
    Show HN: My Anti AI Computer
    punkx.org
    Live Signal Community · 4h old · seen in 2 sources HEATING ×2
  3. 3
    Nvidia's Risky Business
    stratechery.com
    Live Signal Community · 10h old · seen in 3 sources HEATING ×2 +4h lead
  4. 4
    Show HN: My LLM kept getting blocked, so I gave it a browser that looks human
    github.com
    Live Signal Community · 12m old · via Show HN
  5. 5
    Show HN: Webstractor – Pay-as-You-Go Web Data API for AI Agents
    webstractor.com
    Live Signal Community · 12m old · via Show HN
  6. 6
    Show HN: Secure HyperDHT-based agent=>human declarative credentials requester
    peardrop.fyi
    Live Signal Community · 12m old · via Show HN
  7. 7
    Show HN: Advect – autodiff for NumPy and Array API programs
    yaugenst.github.io
    Live Signal Community · 18m old · via Show HN
  8. 8
    Show HN: ThinkingType, an eval measuring if fonts change VLM judgments
    github.com
    Live Signal Community · 18m old · via Show HN
  9. 9
    Show HN: The Complexity Behind Products
    s-1.vercel.app
    Live Signal Community · 24m old · via Show HN
  10. 10
    Misaligned AIs could use killer robots to take over
    lesswrong.com
    Live Signal Community · 24m old · via LessWrong
  11. 11
    Software Is Not Soft
    lesswrong.com
    Live Signal Community · 36m old · via LessWrong
  12. 12
    The Tradeoffs Facing Japan's Economy
    emergingtrajectories.com
    Live Signal Community · 42m old · via Hacker News front
  13. 13
    Show HN: Pulp – Zero-allocation C11 telemetry engine (28M logs/SEC to disk)
    github.com
    Live Signal Community · 42m old · via Show HN
  14. 14
    Show HN: HeyDeacon, AI customer support agent for SaaS founders
    heydeacon.com
    Live Signal Community · 48m old · via Show HN
  15. 15
    Show HN: NotebookLM Calibre Plugin
    github.com
    Live Signal Community · 1h old · via Show HN
  16. 16
    Show HN: HyperSAE – Hyperbolic Sparse Autoencoders for LLM Interpretability
    github.com
    Live Signal Community · 1h old · via Show HN
  17. 17
    Making [etched] holograms with a pen plotter
    blog.jordan.matelsky.com
    Live Signal Community · 7h old · seen in 2 sources HEATING ×2
  18. 18
    Show HN: SmokeOps – describe a flow, get checks you rerun without AI
    github.com
    Live Signal Community · 1h old · via Show HN
  19. 19
    How we used to get jobs: A newspaper classifieds story
    ironicsans.ghost.io
    Live Signal Community · 1h old · via Hacker News front
  20. 20
    Measuring Spurious Correlations with Feature Strength
    lesswrong.com
    Live Signal Community · 1h old · via LessWrong
  21. 21
    Show HN: PR Nutrition, a local rule-based CLI for pull request triage
    github.com
    Live Signal Community · 2h old · via Show HN
  22. 22
    Show HN: TermDOM – HTML, CSS and JavaScript (With a Real DOM) for TUIs and CLIs
    github.com
    Live Signal Community · 2h old · via Show HN
  23. 23
    Show HN: Experimentation platform for simulating agents as users
    docs.514.ax
    Live Signal Community · 2h old · via Show HN
  24. 24
    Show HN: Cjson.cpp, the new fastest-ever (constexpr) JSON parser
    github.com
    Live Signal Community · 2h old · via Show HN
  25. 25
    The SpaceX Sham
    dissentmagazine.org
    Live Signal Community · 2h old · via Hacker News front
  26. 26
    AI governance work needs much better monitoring
    lesswrong.com
    Live Signal Community · 2h old · via LessWrong
  27. 27
    Show HN: Chopi, a macOS filesystem+network sandbox to unleash your agents
    github.com
    Live Signal Community · 2h old · via Show HN
  28. 28
    CSS properties you should know for better text designs
    master.dev
    Live Signal Community · 2h old · via Hacker News front
  29. 29
    Show HN: Zsort, a fast import organizer for Zig
    github.com
    Live Signal Community · 2h old · via Show HN
  30. 30
    Show HN: I used AI to filter AI content from HN
    unslop.news
    Live Signal Community · 2h old · via Show HN
  31. 31
    LLMs Are Starting To Noticeably Accelerate Our Work
    lesswrong.com
    Live Signal Community · 2h old · via LessWrong
  32. 32
    Woman Pulled over at Gunpoint Twice After Flock Camera Glitch
    guessingheadlights.com
    Live Signal Community · 2h old · seen in 3 sources
  33. 33
    Why Go Is an Ideal Language for AI-Assisted Software Engineering
    developers.googleblog.com
    Live Signal Community · 3h old · via Hacker News front
  34. 34
    Show HN: Argmin, challenges for optimizing hard problems
    argmin.dev
    Live Signal Community · 3h old · via Show HN
  35. 35
    Show HN: Blind Box Marble Maze – 3D-printed puzzle solved by tilt and sound [video]
    youtube.com
    Live Signal Community · 3h old · via Show HN
  36. 36
    Show HN: CrewCoder, a free open-source extensible coding-agent for the terminal
    github.com
    Live Signal Community · 3h old · via Show HN
  37. 37
    The fastest double-to-string algorithm you’ve never heard of
    vitaut.net
    Live Signal Community · 3h old · via Lobsters
  38. 38
    Show HN: ExtractBench, an open-source schema extraction benchmark
    github.com
    Live Signal Community · 3h old · via Show HN
  39. 39
    Show HN: ttsalpha/qrcode – Pure SVG React QR code library, zero dependencies
    qrcode.ttsalpha.com
    Live Signal Community · 3h old · via Show HN
  40. 40
    Show HN: Autoclipper – Convert 1 long video in many short clips
    autoclipper.live
    Live Signal Community · 3h old · via Show HN

How Radar works

The gradient. Stories travel through the AI ecosystem in a rough sequence: they appear first in papers (arXiv, Hugging Face) or repos (GitHub), then surface in community discussion (Hacker News, Lobsters, LessWrong), then get interpreted in analysis (operator newsletters and essays). Radar ranks by where a story sits on that gradient. The earlier it is caught, the more lead time you have before it reaches consensus. The spectrum at the top of the page shows the last 24 hours of that flow — every story that entered the watched feeds, counted at the station where it first appeared.

The score. Each story gets a recency-decayed signal score. Every source tier carries a weight and a half-life, so live signal moves fast and fades fast while analysis sources move slowly and stay relevant longer. A story scores higher when two or more independent source families carry it — corroboration, not popularity, which is why five feeds of the same site count once. A small bonus applies when a story has visibly climbed the gradient. Stories past their tier's maximum age expire from the board.

Heating and lead time. A story is heating when it has surfaced in two or more independent source families. When the same story is observed first at an earlier stage and later at a higher one, Radar records the gap in hours — for example, seen on arXiv fourteen hours before it reached the Hacker News front page. That gap is the reader's lead time, and it is a measured span, never an estimate.

The honesty rule. Every value on this page is an observed fact from the feed log — which source carried a story, when, and how many. Radar makes no claim about what a story means; that is the newsletter's job. When a reading does not exist yet — no stories heating, nothing upstream — the page says so rather than inventing one.

Questions

What is the lead-time gradient?
The path a story travels through the AI ecosystem: it appears first in papers (arXiv, Hugging Face) or repos (GitHub), then surfaces in community discussion (Hacker News, Lobsters, LessWrong), then gets interpreted in analysis (operator newsletters, essays). Radar ranks by where a story sits on that path and how far it has travelled.
What does the lead-time spectrum show?
Every story that entered Radar’s watched feeds in the last 24 hours, bucketed by the gradient station where it first appeared — papers, repos, community, or analysis. It is the day’s flow through the whole watched ecosystem, not the composition of the scored top 40 below it: a paper counts in the flow the moment it is observed, even while its signal score is still too low to earn a board row.
How is Radar ranked?
By a recency-decayed signal score: each source tier has a weight and a half-life, a story scores higher when independent source families corroborate it, and a small bonus applies when a story has visibly climbed the gradient. Stories past their tier max age expire from the board. Popularity on a single site is not corroboration.
How often does Radar update?
Hourly. The page is server-rendered and a frozen snapshot is archived at a dated permalink each day, so the record is both current and citable.
What does "heating" mean?
A story has surfaced in two or more independent source families — not two feeds of the same site. It is corroboration, not popularity.
What is the lead time reading?
When the same story is observed first at an earlier gradient stage and later at a higher one, Radar records the gap in hours — for example, seen on arXiv 14 hours before it reached the Hacker News front page. That gap is your lead time. The fires ledger is rolling: a fire ages out with its story, roughly 45 days after the story’s last sighting, so the median lead always describes recent motion.
What sources does Radar watch?
Around 78 verified feeds across five tiers: live signal (Hacker News, Lobsters, GitHub trending, arXiv, Hugging Face papers), AI labs and firehose blogs, operator newsletters, contrarian essayists, and primary analysis. The registry is curated; aggregators are used only to corroborate a story, never to be the first to report it.
Is Radar the newsletter?
No. Radar shows what is moving; the newsletter tells you what to do about it. Radar is the free, public funnel; Vlad’s Newsletter is the weekly operator read.
How to read a row
The spectrum band
A filled flame tick is an early, lead-time-rich stage; a hollow tick is a later stage; a hollow ring on an empty span is a station with nothing on it yet.
Signal class
The tier chip: Live Signal moves fast and decays fast; analysis sources stay relevant longer. The ranker weights each accordingly.
heating
The same story in two or more independent source families — not two feeds of one site.
seen in / via
How many families carried it, or the single source that did.
The radar, dated
Radar shows what's moving. The newsletter tells you what to do about it.

Once a week, the operator read on what actually changed and the move it calls for. No digest, no hype.

Read the newsletter →
Stay close

The next edition lands when this list says it does.

No course. No paywall. Operator playbooks weekly. 10K+ subscribers.