Agreed. The original article and its comments should be restored. Anything else is subterfuge.I had been thinking about making an SB thread on this topic after the Help & Feedback threads got locked, but wanted to take time to reflect some more. I'm glad some sort of response about this wasn't delayed until next week as Aurich suggested it might be. That it's a holiday weekend is no excuse for something that's egregious, this should be considered a pretty house-on-fire moment. Even after reflection though, I really think that I'm not pleased in how this was handled. Thoughts:
I hope this is recognized as the betrayal and serious fuckup it is, and not simply brushed off as a "oh mistakes were made it was a one time thing".
- To reiterate, this was really serious. Particularly in a world of ever growing AI slop, the entire value of a publication like Ars is in trust, trust that we can take what is presented at face value. There were no particular clear tells in the original, which in turn inevitably raises a lot of questions in general. Of course, you made that hard to review, which leads to:
- I do not think that memoryholing both the article and comments thread was the right initial response at all for multiple reasons. Transparency instead of opacity is really important for restoring trust. Hiding everything and locking response threads feels like a cover up, hoping it'll go away. It also destroys both the comments people put effort into, the context they gave, the developer's response, and it denies your customers/readers later the opportunity to learn. Being able to review what was falsely stated is valuable both because it lets people mentally correct anything they though they had learned from Ars, and also serves as an example of where the state of fakery is right now.
Doing a "strike through" of the entire thing with an editors note at the top, taking it off the main page list as well maybe, absolutely fine. But requiring people to go to the Web Archive to find it, making the comments vanish, that was wrong. Particularly given that yeah, of course it's available elsewhere, the Internet doesn't easily forget, and Arsians trend towards being a more technical audience. So the coverup doesn't even work well but feels even worse.
Edit to add: just in general, the forums are as core a draw for a lot of us long term, or more, then the front page articles. Nuking comments completely, short of them being clearly spam or illegal, should be done effectively never imo. It's incredibly discouraging/hurtful to have stuff you've put up wiped out and is disruptive of community, even though 100% Ars (or any platform owner) has the complete legal right to do so. But such power should be treated very gingerly.- This should be a fireable offense full stop, and require personal responsibility particularly given the stated policy that AI tools should not be used at all except for examples of AI itself at a tool level, with full disclosure. So there's no case for "oh I forgot to check" the offense happened when the tool was even invoked by the author(s). Do not circle the wagons.
- This will probably be a catalyzing moment for a bunch of folks which Ars should accept and take more stoically then it might normally.
It's likely the straw that broke the camel's back for many people. I dropped my sub last year and while I can point to the final thing that made me click that cancel button, it was a building frustration.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.
There's ultimately a box somewhere, whether a Mac Mini or rented server or something else, that a human owns or pays for.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.
You do mean the 'human' that drives it right?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>
Sounds handy…I have started using Gemini quite a bit in the last 3-4 weeks, and it is shocking how good it is and how much detailed information it can give me about obscure topics
Oh, maybe less handy…What's also eye-opening is just how often it's completely wrong.
Wait, is this really that shockingly good?It's often still incorrect.
Perhaps replacing it with a screenshot to thwart text crawlers? Maybe in a hard-to-OCR font for bots crazy enough to try?At first I agreed with you, upvoted, and moved on. But then I thought about the implications of doing this in today's world.
5 years ago that would have been an ideal response. Because a human encountering a page of strikethrough text braketed with warnings could reliably be expected to interpret the article as intended.
However ai cannot be trusted to do this and therefore any misinformation contained in the article could be spread to unknowing humans by ai.
There needs to be a more careful solution.
Where I work, a committee weighs in on hiring upper level folks. One of the duties of each of the committee members is to chase down papers, patents, education degrees, etc. We don't split up the work, or just expect that the other members have done it.A plausible, if dumb, explanation is that since the article is a collaboration between two authors, that both of them thought the section in question came from the other author, not recognizing it had been generated, or that the other had not checked it.
++; The original article and comments should never have been disappeared, and should be restored to the site. This is the kind of thing that's routinely covered and mocked on Ars, so I understand there would be no official procedures in a "it could never happen here" sense, but outright deletion is not the appropriate action.Ars’ response here, although well intentioned, raises further questions about their editorial policies and procedures. Deletion of an article with a notice as opaque as this one - “disappearing” the error, essentially - is considered extremely bad practice, arguably worse than simply leaving the article up unaltered. Together with the original fact checking failure it raises significant concerns about the editorial processes and standards of the site.
Many excellent comments and viewpoints about this Charlie Foxtrot, but it took until page 9 to get the best one.This is one of those perfect demonstrations of how AI does not save time. In this case:
1. It did not save time summarizing the article because the first tool failed to work at all.
2. It did not save time because the second tool generated a summary filled with quotes that never existed.
3. It did not save time because the person the article was about had to come and fact check the article himself in the comments.
4. It did not save time because multiple members of the Ars staff had to look into the situation on a weekend.
5. It did not save time because Kyle had to post about his innocence.
6. It did not save time because Benj had to post his explanation and apology.
Well sure. But if we ignore the costs (or better yet make others pay those costs) it’s pure productivity baby!This is one of those perfect demonstrations of how AI does not save time. In this case:
1. It did not save time summarizing the article because the first tool failed to work at all.
2. It did not save time because the second tool generated a summary filled with quotes that never existed.
3. It did not save time because the person the article was about had to come and fact check the article himself in the comments.
4. It did not save time because multiple members of the Ars staff had to look into the situation on a weekend.
5. It did not save time because Kyle had to post about his innocence.
6. It did not save time because Benj had to post his explanation and apology.
How many times over could the article and quotes in question have been checked rather than an author who is paid to write articles handing off his responsibility to a set of tools very well known to output made up results?! I feel confident in saying that a lot of time could have been saved on a lot of people's parts if Benj had just done things the right way in the first place.
THIS is why so many of us are so harsh on any and every story playing up the good side of AI use. The bad sides are always worse!
Contingent on employment law and contractual details, it would be absolutely appropriate for Ars Technica to announce "We have fired our senior AI reporter for an egregious violation of policy and professional ethics in misusing an AI tool to generate false reporting".You want what, a public execution?
And what's being done about the fact that those authors' names were pulled from the retracted piece? Not cool. When people engage in serious journalistic integrity violations, they need to be named.What's being done to/about the authors?
From what I can see, they're both still Ars affiliated:
https://meincmagazine.com/author/benjedwards/
https://meincmagazine.com/author/kyle-orland/
My thoughts:
Ars Technica doesn't owe anyone blood.
Honestly!I bent the rule over not using AI to help write an article (okay, maybe I broke it). But it was not really a violation of trust because my brain was muddled with fever at the time.
Is that better than excusing a monstrously racist remark by claiming drunkenness?
Rules of employment and serious lapses of judgment shouldn’t be discarded when feeling ill. Claiming illness for taking a shortcut to find quotes and not bothering to follow basic journalistic principles and confirming the quote is at best lazy — but is far more than that. It is a violation of basic journalistic principles of reporting the truth.
We don’t excuse comedians, and politicians for unfortunate words when spoken drunk. We don’t allow drunkenness as an excuse for motor vehicle crashes — indeed there are serious legal consequences for that. I don’t think a feverish brain is a valid excuse for not fact checking an attribution and quotation. In the case of driving drunk people are at risk of serious injury or death. Here, I and other readers are confronted with a betrayal of trust in a valued institution. I have valued Airs as a primary information source. I can never trust another article by Mr. Edward’s. I am saddened that the taint of his passive dishonesty has contaminated my trust in Ars itself.
There were already people looking for an excuse to begin with, for one. A permanent loss of subs and possibly forum activity is to be expected (not a whole lot of choice but to curate, balkanize and heavily vet one's journalistic sources these days, and that includes ejecting communities that may have conflicting or even bad faith opinions on other subjects on top of AI related journalistic malpractice, regardless of the risks of trapping oneself into groupthink echo chambers)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.
One aspect of sympathy I'll extend to Ars is that you really do need to be able to expect that your employees are, on the whole, acting in generally good faith. You should have measures in place to catch somebody stealing from the corporate coffers, stuff like that, but it's hard to imagine a system operating with any kind of efficiency when you have to assume everyone is acting in bad faith, all the time. This is even a who-watches-the-watchers situation--Mr. Edwards was not junior staff. He ostensibly runs (hopefully ran) this beat.No they don't. But at the same time, this was a systemic failure. Benj Edwards very clearly violated existing policy, something that a senior writer (covering the AI beat no less) should never, ever do.
But he's not alone, apparently whatever review articles are put through before they're published is woefully insufficient.
Yes, this. Even if writers’ guild union rules require a time for a judicial process; this author should not have another byline. If that means paying him (suspended with pay) for the duration of his contract that is (to me) a reasonable expense. Accepting a false quote without confirmation is a violation of the most basic journalistic duties and integrity. I’m further saddened that Mr. Edwards thought that he could trivialize his dishonesty through a la-dee-dah flimsy excuse of working while ill. That isn’t a valid reason for deciding to ignore one of the most basic journalistic principles.Contingent on employment law and contractual details, it would be absolutely appropriate for Ars Technica to announce "We have fired our senior AI reporter for an egregious violation of policy and professional ethics in misusing an AI tool to generate false reporting".
Frankly, any lesser response will be very worrisome.
Can we at least settle this?Dennis Hastert, 1999 to 2007, Republican Speaker of the House. Convicted pedophile. The person third in line from President was a pedo.
Yes, exactly, if anything let this please end up becoming a teachable moment that can serve to help people realize how dangerous and difficult all of this is becoming.Unfortunate situation. Not ready to join the mob with pitchforks, though. I do hope we get an article about how haphazardly AI is being shoved into everything, now that Ars has clear first hand experience of the pitfalls. It's obviously not enough to say don't do this because bad things, rather we need clear examples (like this) showing why people should take a step back and think about their use of AI.
I think there's a lesson to be learned here for all of us given the amount of AI being shoved down our throats by the tech industry.
If you substitute bobcats for office chairs one time in every 30, you can still have 97% positive feedback.How many true articles do you have to write before you can fabricate one as a treat?
And who wrote it? Doesn’t it seem important that we are allowed to scoff at someone who was this careless?Second this. I get quite a bit of information from Ars articles and would appreciate knowing which one to mentally write off.
Haha, yeah, we can agree on that. Speaker is second in line. I think people brain fart on that a lot, myself included, because the Speaker is third in ranking.While the posts here over-index on those that comment on Sundays, they do show the wide breadth of humanity: maturity, appreciation of due process, susceptibility to reductive thinking, the desire to gossip, and in a few cases abject stupidity.
It further reinforces my current theory: a good chance we are fucked as a species. Funny enough, back with Star Trek, the danger was the nukes. Turns out that's not going to be the root cause.
Can we at least settle this?
- The President is "zero-th" in line. They are currently holding the office
- The VP is first in line, in case something happens
- The Speaker is second in line. Even the phrasing with the word "from" helps to visualize this
Eh i think it’s sort of being pedantic. It depends on how you define “in line”. If the Pres is included in the line, the VP is second and the Speaker third. If the President isn’t included, then VP is first and Speaker second. It’s kind of like the old “banana 0 or banana 1” programming question.Haha, yeah, we can agree on that. Speaker is second in line. I think people brain fart on that a lot, myself included, because the Speaker is third in ranking.