Why this site exists, and what high-signal AI coverage looks like
Most AI coverage today is press-release recycling, hype-cycle commentary, or doomerism. There's a gap for technically literate, source-respecting analysis aimed at builders. This is what we're going to try to fill.
[Placeholder article — Niles will replace the body. Layout and structure are real.]
The gap in AI coverage
If you build with AI tools or follow the research seriously, you've probably noticed the same thing: the volume of coverage has exploded, but the signal-to-noise ratio has gotten worse.
The general-tech press treats every model release as either a revolution or a disappointment, often within the same week. The specialist outlets are better but increasingly captured by access journalism. The independent newsletters are valuable but scattered.
What's missing is a stable place where technically literate readers can get high-signal coverage that respects sources, cites evidence, and doesn't flatten everything into hype or doom.
What we'll do differently
Three commitments:
Source-respecting. Headlines link to originals. Summaries are short. Body text isn't republished without permission. This is the difference between aggregation and theft.
Technically literate. If a paper makes a claim, we'll quote the paper. If a benchmark is gamed, we'll say so. If a release is a wrapper around a known technique, we'll note that too.
Independent. No advertising. No access deals. No incentive to flatter incumbents or punish challengers.
What this isn't
Not a generalist AI ethics outlet. Not a doom shop. Not a vibe-aggregator. Not a place to get hot takes on whether AGI is here.
The cadence
News: daily, when there's something to report. Blog: weekly or so, longer-form, when something deserves analysis. Podcast: roughly biweekly to start, growing if the format works.
One last thing
This site is built and run on private infrastructure. It's plain HTML and CSS served by a Python http.server. There is no JavaScript framework, no analytics, no tracking, no newsletter pop-up. We're trying to model the kind of internet we actually want to read.
If that sounds like something you'd want to follow, the RSS feed is at /feed.xml.