It was caught because the author of the blog post, Scott Shambaugh, posted in the comments that the 2nd half of the article was made up, that the quotes attributed to him were fabricated. Other posters who had read his blog post, affirmed his statement was correct.I think this is the one about an AI bot getting hot and bothered about a rejected push request. Kudos to ARS for catching this and very publicly stating it. <ninjaed>
“AI agents can research individuals, generate personalized narratives, and publish them online at scale,” Shambaugh wrote. “Even if the content is inaccurate or exaggerated, it can become part of a persistent public record.”
– Ars Technica, misquoting me in “After a routine code rejection, an AI agent published a hit piece on someone by name“
Looking into Scott Shambaugh's blog, it appears that the Ars writers used AI to scrape his blog.
Quote above is from his blog: https://web.archive.org/web/2026021...-ai-agent-published-a-hit-piece-on-me-part-2/
I feel like "uphold" is a pretty strong word for what this is. They violated them, and said "we violated them." I will grant that they reiterated their standards that were breached.Thank you for upholding your journalistic standards.
I would say that this is not transparent. It is as opaque as it could possibly be. We already knew that the article had fabricated quotes, thanks to the subject of the article. We didn't know who did the fabricating, and what the consequences would be for them. The only people who didn't know were the ones that didn't see the article, since they took it down rather than leaving it up and putting a notice at the top saying it likely contained fabricated quotes and was under investigation.And a note to our current administration in DC - this is what transparency looks like.
That this happened at Ars is especially distressing. We have covered the risks of overreliance on AI tools for years, and our written policy reflects those concerns.
This is a completely unprofessional retraction, unlike any I've ever seen, that doesn't even name the article being retracted.I sincerely appreciate that Ars pulled the article and issued a retraction @Aurich.
In the interest of full transparency and trust, though, I think it's important that the authors of the article, who appear to have used AI themselves to hallucinate quotes and attributed them to the subject of the article, openly discuss and acknowledge what they did. Unless Ars simply plans to fire them/not accept further contributions from them.
The original article is attributed to Benj Edwards and Kyle Orland. The fact that the article did not meet the journalistic standards of Ars and got retracted is important. But the stance of the authors is equally important because it is a reflection on their future contributions and whether we should trust them.
I hope to see a fuller response from Ars as to what happened and what the full outcome is. But PLEASE, as readers, let’s not speculate on specific individuals and what their role might have been. It’s not fair to anyone to prematurely impugn individual reputations and doesn’t advance the situation in any way. There were two authors and we currently have no way of knowing what their relative responsibilities were.The policy was already pretty clear, and not fabricating quotes seems pretty obvious (AI or not), so this is not exactly helping as a statement. One head should have rolled. Two different writers were listed on the byline; which one is it so I can avoid them in the future? I would assume Benj at this point.
I'll expect nothing short of a full, deep-dive explanation from Ars in a few days. This is quite the event.I'd note that the actual situation is worse than what this retraction notes, given the content of the original story (which I read when it was first posted). I strongly encourage everyone to review Scott's take on the situation at https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/ and the link at the top of that article to the aftermath.
This is worth deep reflection by both developers and news media alike, and I encourage Ars to revisit this topic with a human-written summary of where we suddenly find ourselves with agentic systems.
I'm not dropping my subscription, but I'll be keeping an eye on the situation and if there are no consequences for the authors over the next few months, I won't be resubscribing. I agree that cancelling at this point would be hasty, but if it's just business as usual after this and the authors continue to publish, I can't trust them or this site to be a truthful source. I'm paying because I believe Ars to be a truthful source worth supporting. If it's not, I'm outFirst, dropping your subscription because a single author violated Ars policy and wasn’t caught before publication seems excessive, particularly considering they acted aggressively over the weekend and even admitted precisely what was wrong.
The only thing I don't like about how Ars has handled it so far is that they didn't call attention to which article, and left it to the comments to find which one was retracted. If this were an article that I read and formed opinions on, I'd certainly like to know so that I can re-evaluate those opinions with new information.Two comments:
First, dropping your subscription because a single author violated Ars policy and wasn’t caught before publication seems excessive, particularly considering they acted aggressively over the weekend and even admitted precisely what was wrong.
Second, it gets tricky when possible employee discipline is involved. I think that has to be handled first, before additional public postmortem.
I don’t like it, but I’m also not aware of any publication acting more aggressively and publicly than Ars has (so far) in a similar case.
As my father used to say "It takes 10 rights to right a wrong".Two comments:
First, dropping your subscription because a single author violated Ars policy and wasn’t caught before publication seems excessive, particularly considering they acted aggressively over the weekend and even admitted precisely what was wrong.
Second, it gets tricky when possible employee discipline is involved. I think that has to be handled first, before additional public postmortem.
I don’t like it, but I’m also not aware of any publication acting more aggressively and publicly than Ars has (so far) in a similar case.
I don't understand commenters commending Ars for the statement. It's the bare minimum and reads a little like a dodge. Maybe they need time to figure out how this happened, but until they explain the scope and nature of the issue, how do we trust anything we read here? The source blog takes 10 minutes to read. Why was an AI summary even necessary?I'd note that the actual situation is worse than what this retraction notes, given the content of the original story (which I read when it was first posted). I strongly encourage everyone to review Scott's take on the situation at https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/ and the link at the top of that article to the aftermath.
This is worth deep reflection by both developers and news media alike, and I encourage Ars to revisit this topic with a human-written summary of where we suddenly find ourselves with agentic systems.
fabricated quotations were published in a manner inconsistent with that policy
This is why such notices need to disclose that a port-mortem WILL happen.Second, it gets tricky when possible employee discipline is involved. I think that has to be handled first, before additional public postmortem.
This is where I'm at as well. I'll be keeping an eye on my RSS feed for an update on this situation and how Ars intends to move forward before making any decisions.I'm not dropping my subscription, but I'll be keeping an eye on the situation and if there are no consequences for the authors over the next few months, I won't be resubscribing. I agree that cancelling at this point would be hasty, but if it's just business as usual after this and the authors continue to publish, I can't trust them or this site to be a truthful source. I'm paying because I believe Ars to be a truthful source worth supporting. If it's not, I'm out
I mean, if they were doing an article about how AI can fabricate quotations, I guess it could be consistent with their policy to then use AI to fabricate quotations. Obviously that's a contrived example though...Please elaborate - exactly how can fabricated quotations be published in a manner consistent with the policy?
Which is why I am giving them the benefit of the doubt. This was a really bad event for them. I can’t imagine anyone there being happy with this. I’d imagine they are going to do some serious crackdown on making sure this doesn’t happen again because it’s just about the most damaging thing they could do. I know they’ve lost subscribers over this and that many people will not give them another chance.As my father used to say "It takes 10 rights to right a wrong".
Once that trust is lost, it's nearly impossible to get back. Public trust is a finicky and finite thing.
Agreed, I am absolutely willing to give ars some time to produce a quality response, especially considering the weekend timing of the incident. The response so far is sufficient as a temporary measure.I'll expect nothing short of a full, deep-dive explanation from Ars in a few days. This is quite the event.