Why this exists
AI news arrives everywhere at once, all day: dozens of sources, hundreds of items, and the same announcement told five different ways. Reading it by hand is exhausting, and it still means missing the one that mattered.
HOlO reads it, decides what carries a signal, and hands you the ranked picture once a day. That is the whole product: no feed to babysit, no notification to chase.
Most days nothing changes the world, and the digest says so. A quiet morning is published as a quiet morning; the bar is fixed, so the page is never padded to look full. The number of signals follows the day, never the other way round.
This morning's run, start to finish: about 4 minutes, unattended. Every narrowing is a written rule (the score bar, the duplicate check, the daily cap), never a mood.
What it is
A ranked digest, not a firehose. Every item is scored on information density and on whether you can do something with it. Items several independent sources carried rank higher, because corroboration is the strongest evidence an automated reader has.
What survives the bar is summarised, deduplicated against every address published in the last 90 days and against the same story inside the day, then cut to a daily quota, and published with a why-now and the evidence behind it.
- 01Discover
One engine reads the day's AI sources and keeps what carries a signal.
- 02Analyze
Every item is scored, cross-checked against the other sources and given a why-now.
- 03Disrupt
You get the ranked picture, not another feed to scroll.
What it is not
- No infinite scroll, no autoplay, no algorithm guessing what holds you.
- No engagement loop: nothing here is optimised to keep you on the page.
- No token, no airdrop, no waitlist.
- No ads, no sponsored placement, no paid ranking.
- No tracking, and no profiling on this surface. Signing in gives you a name to vote with, and that is all it is for.
- No comments, no follower counts, no trending sidebar.
- No personalisation here: every reader opens the same digest, in the same order.
- No ranking by popularity inside the digest: votes never reorder the day's signals. On the ideas page they do rank the build directions, and that page says so.
- Not a newsletter, not a chatbot, not a summary of someone else's summary.
How to read a signal
Each signal carries four labelled cells: why now, the reason it matters today; evidence, the facts it rests on, with names, numbers and dates; topic; and source. A corroboration line says how many sources carried the same story.
Show HN: MyA11yReport MCP, Build and test accessible websites with AI
- why now
- New local MCP server lets AI agents audit website accessibility, released now for indie hackers.
- what changes
- This enables AI agents to autonomously run comprehensive accessibility audits, including WCAG 2.2 contrast and interactive elements, all locally.
- to do
- Install with 'npm i -g mya11yreport-mcp', download Chromium, and add the server to your MCP client to start agent-run audits.
- Local MCP server gives AI agents axe-core scans, tab order, and WCAG 2.2 contrast checks
- Runs entirely on the machine: no account, no API key, data never leaves the host
- Requires Node.js 20+ and a one-time 150 MB Chromium download
Two answers are recorded per signal: good, maybe, don't. They are the only thing a reader can change, and they are public.
Items from Chinese sources reach the engine in Chinese, and their source is always named, so you can see where one came from. The engine writes its own English headline and reading for them: the summary, the why-now, and the labelled cells. It never reprints the original words as if they were ours.
How the score is built
The score is information density multiplied by usefulness. Density comes from concrete facts: numbers, product names, versions, prices. Usefulness means the reader can do something, or judge better, after reading. Vague opinion, marketing copy and unsupported predictions are capped at 4.
To reach an 8 or morein a given topic, the item has to satisfy that topic's conditions:
- new model or new technique
- benchmark data or a comparison with existing models; API availability, pricing or open-source status; a working demo or user feedback. Missing any two: minus 2.
- one-person business case
- concrete revenue figures, what the product is, and how it found customers. Without a revenue figure it is capped at 6.
- tool or agent workflow
- a reusable prompt or steps with a before and after, or a specific stack with real effect or cost data. For an open-source repository, a clear description and use case are enough.
- funding news
- round size, investors and what the business does, plus a valuation or a comparison with the previous round. Without the amount it is capped at 6.
Four deductions apply everywhere, and none of them is optional: a piece that reads as a press release or official promotion is capped at 3, a pure repost or aggregation loses 2, anything older than 14 days loses 1, and a headline the body does not back loses 3.
An item is kept when its score is 5 or more andits topic is not "unrelated". A well-scored item on an unrelated subject is still dropped.
DeepSeek desktop version quietly launched; Muse goes viral, Zuckerberg becomes world's fourth richest; OpenAI reportedly preparing ProMax subscription tier, monthly fee may reach $500-600
极客公园
Trump administration's WISeR project uses AI to approve Medicare preauthorization, rejection rate and incentive structure spark controversy
AI热榜
Both were published this morning, and the gap between them is the whole point: the bar keeps what is useful, not what is loud.
65 items passed the bar this morning; the quota kept 33. The cap exists because a digest of everything above the bar would be a firehose again.
Where it comes from
38 sources, read in parallel every morning. 29 are in English, 9 in Chinese. No paywalled wire. Mostly publications, newsletters, forums and code repositories, each read at its own address: one of them is a curated hot list, and it is counted as one source among the others.
- Reddit r/SideProject5 failures, last read 2026-09-21
- HackerNoon AI
- Reddit r/SideProject
- Reddit r/Entrepreneur
- Ben's Bites
- The Rundown AI
- One Useful Thing
- Zara's Newsletter
- TLDR AI
- Latent Space
- Lenny's Newsletter
- Simon Willison's Blog
- Hugging Face Blog
- Hacker News Show HN
- Hacker News Best
- Lobsters
- DEV Community
- GitHub Trending
- TechCrunch AI
- MIT Technology Review AI
- Nature
- Quanta Magazine
- Trends.vc
- Product Hunt
- Practical Ecommerce
- Shopify Blog
- Marketing AI Institute
- Search Engine Journal (Ecommerce)
- eCommerceFuel
- eCommerceBytes
- 量子位
- 量子位（公众号）
- 新智元
- 机器之心
- 36氪
- 少数派
- 爱范儿
- 极客公园
- AI热榜
A source that stops answering is retired after five consecutive failures, with the reason and the way back recorded in the config. An address that dies is our failure to report, never a silence to hide.
The engine
One scheduled run a day: fetch, pre-filter on length and keywords, score every item with a model, deduplicate, apply the quota, then write the English edition of each surviving signal. That edition carries the headline, tags, summary, why-now and the cells above. This morning's run took about 4 minutes and needed nobody watching.
- 01fetchevery source read in parallel137 items
- 02filterlength and keywords, before any model is called132 unseen
- 03scoreone model call per item, against the published bar65 pass
- 04cross-checkthe same story seen across independent sources3 corroborated
- 05deduplicatenear-identical write-ups removedminus 8
- 06capthe daily quota, so the digest stays a digest33 kept
- 07writeEnglish headline, tags, summary, why-now and the cellson 33
- 08publishthe new digest replaces yesterday's
The count follows the day, not the other way round: 13 signals on a thin morning, 34 on a thick one. Nothing is padded to fill a page.
The engine is private; the outputs are not. Everything published stays readable, and the digest being served is the one the run wrote. There is no editing in the product: the one hand correction ever made, the day the English edition shipped, is recorded in the operations log rather than hidden.
A machine decides what you see. It is wrong sometimes: a signal can be dull, a good one can be dropped. That is exactly why the bar is published, why the sources are listed, and why the votes exist. The reasoning can be checked against the result, and said out loud.
Questions
- What happens to items from Chinese sources?
- Items from Chinese sources arrive in Chinese. The engine writes its own English headline, summary, why-now and cells for them, and the source is always named, so a Chinese item is never passed off as an English one. The original text is not reprinted on this surface.
- What happens when a run fails?
- Nothing is published. Yesterday's digest stays up, and the next run starts from the same history, so an item is never served twice as if it were new.
- Why 05:30 UTC?
- One scan a day, at a fixed hour, so the digest is there when you look for it and a thin morning is visible as a thin morning. A second scan would mostly find the same stories.
- Can a signal be edited by hand?
- No. What the run wrote is what is served. The only human input is the configuration: which sources are read, and how the bar is worded.
- What do the votes change?
- On the digest, nothing: the order you read is the score. On the ideas page, the votes do rank the build directions, and that page says so. Everywhere else they are recorded, counted and public, so a reader can see what others made of a signal.
- Why keep 90 days of history?
- So a story already published is not served again as new, and so the archive can be read back. Six mornings are online so far, and older ones accumulate.