Mycroft: Turning Hacker News into a Verified AI Attention Signal

A week nine update on Mycroft shows how a title-based filtering fix corrected a company attribution bug and how the project now ships an honest, versioned JSON signal.

1:51 video3 min readWatch on YouTube

A sentiment pipeline is only as good as its attribution logic, and this update is a case study in what happens when that logic is wrong. Mycroft, an ongoing Humanitarians AI Fellows project, turns Hacker News discussion into an attention signal for the AI sector, scoring how much buzz major AI companies are getting from the developer community. In week nine, Om Mali walks through a real bug in that scoring, how it got fixed, and what the project is still honest about not knowing.

What Mycroft measures

The project distills Hacker News activity into a score of how much genuine attention each major AI company is getting from developers, moving past raw post counts toward something closer to what people are actually saying and thinking about a company. That signal only matters if it's attributing the right conversations to the right companies, which is where week nine's real work happened.

The attribution bug

The top story for each company had been selected purely by point count, with no check on whether the story was actually about that company. That approach broke in a concrete way: a post about Bento, a slide-deck tool that merely mentioned Claude and ChatGPT in passing, became the top story for both OpenAI and Anthropic. The result was a confident, well-formed, and completely wrong signal, one that ended up "praising presentation software" as if it were AI sector news.

The fix: title-based filtering

The fix was simple and strict: a story only counts toward a company's score if that company's name appears in the title. After applying that rule, OpenAI's top stories became real OpenAI news, and Anthropic's became real Claude stories. That's a meaningfully better result, but Mali is careful not to oversell it. Anthropic's top stories are now often about third-party tools built for Claude, not about Anthropic the company itself. A title can name a product without the story actually being about the company behind it, and the update draws that boundary explicitly rather than papering over it.

A versioned JSON contract other systems can use

The second half of the update is about usability. The signal had been generating every run and going nowhere, so it was formalized into a versioned JSON contract with a pull endpoint. That endpoint returns score, momentum, and sentiment per company, structured so other systems can consume it directly rather than scraping a human-readable report. Companies with no comments in a given run are explicitly flagged as degraded data rather than silently omitted or faked.

Key takeaways

  • Mycroft scores how much attention major AI companies are getting from Hacker News discussion, distilled into a usable signal.
  • A points-only top-story selection let an unrelated slide-deck tool get misattributed as top news for both OpenAI and Anthropic.
  • The fix requires a company's name to appear in the story title before that story counts toward its score.
  • Even after the fix, a title naming a product isn't the same as a story being about the company, and the project states that limitation openly.
  • A new versioned JSON endpoint returns score, momentum, and sentiment per company so other systems can pull the data directly.
  • Missing or thin data is flagged as degraded rather than hidden, which the project treats as its most important feature.

Who this is for

This update is aimed at anyone building or evaluating sentiment and attention-tracking pipelines, particularly other Humanitarians AI Fellows working on data-driven projects. The bigger lesson travels well beyond Mycroft: a pipeline that admits what it doesn't know is more useful than one that looks polished but is quietly wrong.

Chapters

  1. 0:00What is Mycroft? Scoring AI buzz from the developer community
  2. 0:25The Attribution Bug: Why "top stories" aren't always relevant
  3. 0:50The Fix: Ensuring stories only count if the company is in the title
  4. 1:15Defining Limits: Distinguishing between companies and third-party tools
  5. 1:35Technical Update: The versioned JSON contract and endpoint
Full transcript(auto-generated, with timestamps)

What is Mycroft? Scoring AI buzz from the developer community

[0:00]Hi, I'm Om Malik. This video covers week nine of Mic Roth, my Hacker News AI attention signal project. It covers a real attribution bug I found and fixed, the new version JSON endpoint other systems can now use, and an honest look at what the signal still doesn't know. This project turns Hacker News into an attention signal for the AI sector. It scores how much buzz each major AI company is getting from the developer community and distills what people

The Attribution Bug: Why "top stories" aren't always relevant

[0:25]Actually think about them. The recent work asked three harder questions. Is that output right? Can other systems use it? And is it honest about its limits? The top story for each company was picked purely by points. So, this post Bento, a slide tool that only mentioned Claude and Chat GPT, became the top story for both OpenAI and Anthropic. Their opinions ended up praising presentation software. The fix, a story only counts if the company's name is in the title. After it, OpenAI's

The Fix: Ensuring stories only count if the company is in the title

[0:51]Stories are real OpenAI news, and Anthropic's are real Claude stories, confident, well-formed, and wrong. Now corrected, but I won't oversell it. Anthropic's stories are real, but they're third-party tools for Claude, not the company. A title can name a product without being about it. I'm showing that boundary, not hiding it. Second, the signal was generated every run and going nowhere. So, I formalized it into a version JSON contract and

Defining Limits: Distinguishing between companies and third-party tools

[1:16]Built a pull endpoint. This is the literal payload it returns, score, momentum, sentiment per company. And here's that same contract read as one row per company. The companies that had no comments are honestly flagged as degraded, not hidden, and the whole thing is ready for other systems to consume. What's built is built and

Technical Update: The versioned JSON contract and endpoint

[1:36]Verified, the fix, the live endpoint, the digest, the alerts, the tests. This work didn't add a flashy feature. It made the pipeline correct where it could be, honest where it couldn't, and usable by others. The best thing I built was the guardrail that admits what it doesn't know.

More from Mycroft Financial AI

Humanitarians AI Lyrical Literacy Project