I've seen Claude and ChatGPT happily hallucinate whole APIs for D3 on multiple occasions, which should be really well represented in the training sets.
With many existing systems, you can pull documentation into context pretty quickly to prevent the hallucination of APIs. In the near future it's obvious how that could be done automatically. I put my engine on the ground, ran it and it didn't even go anywhere; Ford will never beat horses.
Maybe a site like this should try to root-out the "root source" of information - official press releases or press conferences, eye-witness accounts.
I think some editorializing is worthwhile to place things in context and to decide what information to put together into a readable article, but things could be more explicit and should always link to the source material.
I'd personally pay for that. It feels like 90% of the "news" I see these days is just some site telephoning what a different reporter said. I regularly see "study finds x" articles that completely bury the original academic source. Often, "politician said x" articles that spend a lot of time going over everyone's reactions to whatever the politician said without letting me have the full video or press release where he actually said it.
This would also fix an issue I'm seeing on Kite where some stories seem to be the same thing from different angles (one article about the Texas floods is directly above an article about how the Texas floods are "testing FEMA", and there are two separate articles for the recent Trump-Netanyahu deal, one in World and one in USA. X's CEO resigning is three different articles in different feeds. The Business tab has two different articles about Trump tariffs that could really be one article).