News outlets AI fact-checker cannot read
30 July 2026 AI fact-checking measurement The news outlets an AI fact-checker cannot read I tried to make my fact-checking tool prefer reputable sources. Turns out 16 of the most reputable ones refuse to talk to it. Their reporting still comes back, wearing someone else's URL.
- ▪30 July 2026 AI fact-checking measurement The news outlets an AI fact-checker cannot read I tried to make my fact-checking tool prefer reputable sources.
- ▪Turns out 16 of the most reputable ones refuse to talk to it.
- ▪Their reporting still comes back, wearing someone else's URL.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,445 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | korniienko.dev |
| Canonical URL | https://korniienko.dev/blog/news-outlets-ai-cannot-read/ |
| Publication time | Tue, 11 Aug 2026 13:09:44 +0000 |
| Retrieval time | 2026-08-11T13:20:43.951Z |
| Last seen | 2026-08-11T13:20:43.951Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | E0glcHQgZL3P · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
30 July 2026 AI fact-checking measurement The news outlets an AI fact-checker cannot read I tried to make my fact-checking tool prefer reputable sources. Turns out 16 of the most reputable ones refuse to talk to it. Their reporting still comes back, wearing someone else's URL. Someone on Hacker News gave me a good suggestion: tell the model to “use credible sources”. You can watch its reasoning and see it rule out random blogs and prefer outlets with a reputation for fact checking. I said I’d test it and publish the comparison either way. Test failed. What I found instead is more interesting, at least to anyone building tools that ask a model to check facts against the open web. Sixteen of the news organisations with the strongest fact-checking reputations refuse the crawler.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at korniienko.dev.
Discussion
0 commentsMore from korniienko.dev
