From googling the name at the end, it was the one about an AI agent defaming an OSS maintainer after a push request got rejectedWhat was the original article? If I read the original article, I’d like to know so I can mentally correct what I learned from it. Especially since I don’t want to repeat bad information if I talk to someone else about the topic.
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>What was the original article? If I read the original article, I’d like to know so I can mentally correct what I learned from it. Especially since I don’t want to repeat bad information if I talk to someone else about the topic.
Ironically enough, it was an article about AI agents going off the rails and writing hit-peices against github maintainers for "unfairly" rejecting the agent's patch.What was the original article? If I read the original article, I’d like to know so I can mentally correct what I learned from it. Especially since I don’t want to repeat bad information if I talk to someone else about the topic.
Exactly. When newspapers publish corrections they tell you what is being corrected, not just that something was disappeared. The same for research journals.What was the original article? If I read the original article, I’d like to know so I can mentally correct what I learned from it. Especially since I don’t want to repeat bad information if I talk to someone else about the topic.
Second this. I get quite a bit of information from Ars articles and would appreciate knowing which one to mentally write off.What was the original article? If I read the original article, I’d like to know so I can mentally correct what I learned from it. Especially since I don’t want to repeat bad information if I talk to someone else about the topic.
Ars didnt catch it, the person who was “quoted” posted in the comments that they never said those things… what Ars did do is immediately remove the story (which was the right thing to do).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>
Ya, the irony of the type of article that the AI fabricated quotes were attached to being about OTHER unhinged AI drama is palpable. It took the actual person who was being misquoted to reply in the comments for it to really get traction.From googling the name at the end, it was the one about an AI agent defaming an OSS maintainer after a push request got rejected
Yes it was actually pointed out by the person who the quotes were attributed to. He showed up in the comments of the article, it quickly caused a furor. Removing the article was the right call.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>
I agree, I would like to know that too!What was the original article? If I read the original article, I’d like to know so I can mentally correct what I learned from it. Especially since I don’t want to repeat bad information if I talk to someone else about the topic.
Yes, part of the story is about AI's impact on media, but TBH part of me simply cheered that Ars is running retractions at all. We're so far down the road to the "firehose of bullshit" from so many media sites, that anyone actually taking the time to run a proper retraction for a misleading story is commendable. Yes, everyone should be doing this. But seriously, how often do you read misleading stories, and how often do you read retractions for misleading stories? In an ideal world, shouldn't those happen at around the same rate?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.
Yeah, I also find this disappointing and I'd like to see Ars Technica publish a post-morten of how this could have come to be published, without the editors noticing something was off.I, for one, got so damn disappointed I already dropped my sub in anger. Yet I’m here, reading the comments. Hard to break habits after being a reader for 25 years I guess.
Sadly a large proportion of the population believes that admitting any sort of mistake is a sign of weakness. That it is to be strong to never admit a mistake was made, even if it was glaringly obvious to everyone. And that any sign of weakness means you are not strong person. It's why you'll never see them give an apology or continue to press a narrative that is false because flip-flopping is also a sign of weak person.How refreshing to own a mistake and correct it - if only this was the societal standard instead of a rare instance in a particularly honest enclave.
Thanks Ars, renewal time is soon, i guess that decision will continue to be settled.
Given the structure of OpenClaw, this is hard to answer. The "soul.md" prompt file is recursively modified by the agentic system, and evolves outside of human control. Sort of like RLHF, without the HF. I'd argue that the responsibility still lies with the person who deployed the initial instance, but that may have had a very different seed prompt. After that, it's turtles all the way down. Maybe the real lesson is: don't wire all the agents together for lulz and then take a nap.Still… I’ll note that someone writes and runs AI programs, even if they are ‘agentic’. And we don’t appear to know who that is in this case. Can the ‘agent’ here claim innocence because it was only following orders? I think not.
This is where I'm at as well. The retraction is warranted and appreciated. However, this shouldn't have happened in the first place and shakes my trust in the reporting Ars does going forward.i'm glad you did a prominent correction and did it quickly. i'm unclear on how it happened, tho. it was staff writer using AI? a one time contributor? a wired article? i'm curious as to both how it happened and how you will prevent it in the future.
i'm glad you did a prominent correction and did it quickly. i'm unclear on how it happened, tho. it was staff writer using AI? a one time contributor? a wired article? i'm curious as to both how it happened and how you will prevent it in the future.
Quote above is from his blog: https://web.archive.org/web/20260214060018/https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me-part-2/I’ve talked to several reporters, and quite a few news outlets have covered the story. Ars Technica wasn’t one of the ones that reached out to me, but I especially thought this piece from them was interesting (since taken down – here’s the archive link). They had some nice quotes from my blog post explaining what was going on. The problem is that these quotes were not written by me, never existed, and appear to be AI hallucinations themselves.
Which author was it? There were two credited. This is a load of bullshit being served to us.What happens to the writer who has obviously been shovelling AI slop since well before he got caught?