hckrnws

Odd that there's no link to the retracted article.

Thread on Arstechnica forum: https://arstechnica.com/civis/threads/editor%E2%80%99s-note-...

The retracted article: https://web.archive.org/web/20260213194851/https://arstechni...

The articles authors are listed on that page as: Benj Edwards and Kyle Orland.

[dead]

Benj Edwards, one of the authors, accepted responsibility in a bluesky post[0]. He lists some extenuating circumstances[1], but takes full responsibility. Time will tell if it's a one-off thing or not I guess.

[0] https://bsky.app/profile/benjedwards.com/post/3mewgow6ch22p

[1] your mileage may vary on how much you believe it and how much slack you want to cut him if you do

It's not really important whether it's a one-off thing with this one guy, he's not relevant in the big picture. To the extent that he deindividualizes his labor he's just one more fungible operator of AI anyway.

People are making a bigger deal about it than this one article or site warrants because of ongoing discourse about whether LLM tech will regularly and inevitably lead to these mistakes. We're all starting to get sick of hearing about it, but this keeps happening.

Bluesky post by Benj (one of the authors of the article). https://bsky.app/profile/benjedwards.com/post/3mewgow6ch22p

He admits to using an AI tool, says he was sick and did dumb things. He does clear Kyle (the other author).

I have to say this rings hollow to me. "In the throes of COVID" is certainly not the time I have been inspired to experiment with new tools I've never used before. This sounds like the cop-out of someone who already uses said tools routinely. I think it's also awfully convenient to fall on the sword and absolve the senior employee on the byline of all responsibility for an article that bears his name on it. Nor does being sick really excuse this. Shoddy work is one thing, turning to a fabrication tool is another.

I'm sure I will be criticised for being a cynic but I can't not be cynical when this is the state of journalism. I wish I could live in a world where people who are paid to report on things that happen in reality would, in fact, write about things that actually happened in reality.

People put a lot of weight on blame-free post-mortems and not punishing people who make "mistakes", but I believe that has to stop at the level of malice. Falsifying quotes is malice. Fire the malicious party or everything else you say is worthless.

That don't actually say it's a blame free post-mortem, nor is it worded as such. They do say it's their policy not to publish AI generated anything unless specifically labelled. So the assumption would be that someone didn't follow policy and there will be repercussions.

The problem is people on the Internet, hn included, always howl for maximalist repercussions every time. ie someone should be fired. I don't see that as a healthy or proportionate response, I hope they just reinforce that policy and everyone keeps their jobs and learns a little.

Correct, I only mentioned the blame-free post-mortem thing to head off the usual excuses.

> I don't see that as a healthy or proportionate response,

Again, correct. It's only appropriate in cases of malice.

Yes. This is being treated as thought it were a mistake, and oh, humans make mistakes! But it was no mistake. Possibly it was a mistake on the part of whoever was responsible for reviewing the article before publication didn't catch it. But plagiariasm and fabrication require malicious intent, and the authors responsible engaged in both.

There’s no malice if there was no intention of falsifying quotes. Using a flawed tool doesn’t count as intention.

Outsourcing your job as a journalist to a chatbot that you know for a fact falsifies quotes (and everything else it generates) is absolutely intentional.

It's intentionally reckless, not intentionally harmful or intentionally falsifying quotes. I am sure they would have preferred if it hadn't falsified any quotes.

He's on the AI beat, if he is unaware that a chatbot will fabricate quotes and didn't verify them that is a level of reckless incompetence that warrants firing

Yeah! We can call things reckless incompetence without calling them malice!

The tool when working as intended makes up quotes. Passing that off as journalism is either malicious or unacceptably incompetent.

Outsourcing writing to a bot without attribution may not be malicious, but it does strain integrity.

I don't think the article was written by an LLM; it doesn't read like it, it reads like it was written by actual people.

My assumption is that one of the authors used something like Perplexity to gather information about what happened. Since Shambaugh blocks AI company bots from accessing his blog, it did not get actual quotes from him, and instead hallucinated them.

They absolutely should have validated the quotes, but this isn't the same thing as just having an LLM write the whole article.

I also think this "apology" article sucks, I want to know specifically what happened and what they are doing to fix it.

The issues with such tools are highly documented though. If you’re going to use a tool with known issues you’d better do your best to cover for them.

> Using a flawed tool doesn’t count as intention.

"Ars Technica does not permit the publication of AI-generated material unless it is clearly labeled and presented for demonstration purposes. That rule is not optional, and it was not followed here."

They aren't allowed to use the tool, so there was clearly intention.

They're expected by policy to not use AI. Lying about using AI is also malice.

It's a reckless disregard for the readers and the subjects of the article. Still not malice though, which is about intent to harm.

Lying is intent to deceive. Deception is harm. This is not complicated.

I think you're reading a lot of intentionality into the situation what may be present, but I have not seen information confirming or really even suggesting that it is. Did someone challenge them, "was AI used in the creation of this article?" and they denied it? I see no evidence of that.

Seems like ordinary, everyday corner cutting to me. I don't think that rises to the level of malice. Maybe if we go through their past articles and establish it as a pattern of behavior.

That's not a defence to be clear. Journalists should be held to a higher standard than that. I wouldn't be surprised if someone with "senior" in their title was fired for something like this. But I think this malice framing is unhelpful to understanding what happened.

> Ars Technica does not permit the publication of AI-generated material unless it is clearly labeled and presented for demonstration purposes. That rule is not optional, and it was not followed here.

By submitting this work they warranted that it was their own. Requiring an explicit false statement to qualify as a lie excludes many of the most harmful cases of deception.

Have you ever gone through a stop sign without coming to a complete stop? Was that dishonesty?

You can absolutely lie through omission, I just don't see evidence that that is a better hypothesis than corner cutting in this particular case. I am open to more evidence coming out. I wouldn't be shocked to hear in a few days that there was other bad behavior from this author. I just don't see those facts in evidence, at this moment. And I think calling it malice departs from the facts in evidence.

Presumably keeping to the facts in evidence is important to us all, right? That's why we all acknowledge this as a significant problem?

We see a typical issue in modern online media: The policy is to not use AI, but he demands of content created per day makes it very difficult to not use AI... so the end result is undisclosed AI. This is all over the old blogosphere publications, regardless of who owns them. The ad revenue per article is just not great

At this point anyone reporting on tech should know the problems with AI. As such even if AI is used for research and articles are written on that output by human there is still absolute unquestionable expectation to do the standard manual verification of facts. Not doing it is pure malice.

I don’t see how you could know that without more information. Using an AI tool doesn’t imply that they thought it would make up quotes. It might just be careless.

Assuming malice without investigating is itself careless.

we are fucking doomed holy shit

we're really at the point where people are just writing off a journalist passing off their job to a chatgpt prompt as though that's a normal and defensible thing to be doing

No one said it was defensible. They drew a distinction between incompetence and malice. Let's not misquote each other here in the comments.

Even if it didn't fabricate quotes wholesale, taking an LLM's output and claiming it as your own writing is textbook plagiarism, which is malicious intent. Then, if you know that LLMs are next-token-prediction-engines that have no concept of "truth" and are programmed solely to generate probabilistically-likely text with no specific mechanism of anchoring to "reality" or "facts", and you use that output in a journal that (ostensibly) exists for the reason of presenting factual information to readers, you are engaging in a second layer of malicious intent. It would take an astounding level of incompetence for a tech journal writer to not be aware of the fact that LLMs do not generate factual output reliably, and it beggars belief given that one of the authors has worked at Ars for 14 years. If they are that incompetent, they should probably be fired on that basis anyways. But even if they are that incompetent, that still only covers one half of their malicious intent.

The article in question appears to me to be written by a human (excluding what's in quotation marks), but of course neither of us has a crystal ball. Are there particular parts of it that you would flag as generated?

Honestly I'm just not astounded by that level of incompetence. I'm not saying I'm impressed or that's it's okay. But I've heard much worse stories of journalistic malpractice. It's a topical, disposable article. Again, that doesn't justify anything, but it doesn't surprise me that a short summary of a series of forum exchanges and blog posts was low effort.

I don't believe there is any greater journalistic malpractice than fabrication. Sure, there are worse cases of such malpractice in the world given the low importance of the topic, but journalists should be reporting the truth on anything they deem important enough to write about. Cutting corners on the truth, of all things, is the greatest dereliction of their duty, and undermines trust in journalism altogether, which in turn undermines our collective society as we no longer work from a shared understanding of reality owing to our inability to trust people who report on it. I've observed that journalists tend to have unbelievably inflated egos and tout themselves as the fourth estate that upholds all of free society, and yet their behaviour does not actually comport with that and is rather actively detrimental in the modern era.

I also do not believe this was a genuine result of incompetence. I entertained that it is possible, but that would be the most charitable view possible, and I don't think the benefit of doubt is earned in this case. They routinely cover LLM stories, the retracted article being about that very subject matter, so I have very little reason to believe they are ignorant about LLM hallucinations. If it were a political journalist or something, I would be more inclined to give the ignorance defense credit, but as it is we have every reason to believe they know what LLMs are and still acted with intention, completely disregarding the duty they owe to their readers to report facts.

> I don't believe there is any greater journalistic malpractice than fabrication. Sure, there are worse cases of such malpractice...

That's more or less what I mean. It was only a few notches above listicle to begin with. I don't think they intended to fabricate quotes. I think they didn't take the necessary time because it's a low-stakes, low-quality article to begin with. With a short shelf life, so it's only valuable if published quickly.

> I also do not believe this was a genuine result of incompetence.

So your hypothesis is that they intentionally made up quotes that were pretty obviously going to be immediately spotted and damage their career? I don't think you think that, but I don't understand what the alternative you're proposing is.

I also feel compelled to point out you've abandoned your claim that the article was generated. I get that you feel passionately about this, and you're right to be passionate about accuracy, but I think that may be leading you into ad-hoc argumentation rather than more rational appraisal of the facts. I think there's a stronger and more coherent argument for your position that you've not taken the time to flesh out. That isn't really a criticism and it isn't my business, but I do think you ought to be aware of it.

I really want to stress that I don't think you're wrong to feel as you do and the author really did fuck up. I just feel we, as a community in this thread, are imputing things beyond what is in evidence and I'm trying to push back on that.

What I'm saying is that I believe they do not care about the truth, and intentionally chose to offload their work to LLMs, knowing that LLMs do not produce truth, because it does not matter to them. Is there any indication that this has damaged their career in any way? It seems to me that it's likely they do not care about the truth because Ars Technica does not care about the truth, as long as the disregard isn't so blatant that it causes a PR issue.

> I also feel compelled to point out you've abandoned your claim that the article was generated.

As you've pointed out, neither of us has a crystal ball, and I can't definitively prove the extent of their usage. However, why would I have any reason to believe their LLM usage stops merely at fabricating quotes? I think you are again engaging in the most charitable position possible, for things that I think are probably 98 or 99% likely to be the result of malicious intent. It seems overwhelmingly likely to me that someone who prompts an LLM to source their "facts" would also prompt an LLM to write for them - it doesn't really make sense to be opposed to using an LLM to write on your behalf but not be opposed to it sourcing stories on your behalf. All the more so if your rationale as the author is that the story is unimportant, beneath you, and not worth the time to research.

> I think you are again engaging in the most charitable position possible, ...

Yeah, that's accurate. I will turn a dime the moment I receive evidence that this was routine for this author or systemic for Ars. But yes, I'm assuming good faith (especially on Ars' part), and that's generally how I operate. I guess I'm an optimist, and I guess I can't ask you to be one.

What are they changing to prevent this from happening in the future? Why was the use of LLMs not disclosed in the original article? Do they host any other articles covertly generated by LLMs?

As far as I can tell, the pulled article had no obvious tells and was caught only because the quotes were entirely made up. Surely it's not the only one, though?

My read is, "Oops someone made a mistake and got caught. That shouldn't have happened. Let's do better in the future." and that's about it.

When an article is retracted it's standard to at least mention the title and what specific information was incorrect so that anyone who may have read, cited or linked it is informed what information was inaccurate. That's actually the point of a retraction and without it this non-standard retraction has no utility except being a fig leaf for Ars to prevent external reporting becoming a bigger story.

In the comments I found a link to the retracted article: https://arstechnica.com/ai/2026/02/after-a-routine-code-reje.... Now that I know which article, I know it's one I read. I remember the basic facts of what was reported but I don't recall the specifics of any quotes. Usually quotes in a news article support or contextualize the related facts being reported. This non-standard retraction leaves me uncertain if all the facts reported were accurate.

It's also common to provide at least a brief description of how the error happened and the steps the publication will take to prevent future occurrences.. I assume any info on how it happened is missing because none of it looks good for Ars but why no details on policy changes?

Edit to add more info: I hadn't yet read the now-retracted original article on achive.org. Now that I have I think this may be much more interesting than just another case of "lazy reporter uses LLM to write article". Scott, the person originally misquoted, also suspects something stranger is going on.

> "This blog you’re on right now is set up to block AI agents from scraping it (I actually spent some time yesterday trying to disable that but couldn’t figure out how). My guess is that the authors asked ChatGPT or similar to either go grab quotes or write the article wholesale. When it couldn’t access the page it generated these plausible quotes instead, and no fact check was performed." https://theshamblog.com/an-ai-agent-published-a-hit-piece-on...

My theory is a bit different than Scott's: Ars appears to use an automated tool which adds text links to articles to increase traffic to any related articles already on Ars. If that tool is now LLM-based to allow auto-generating links based on concepts instead of just keywords, perhaps it mistakenly has unconstrained access to changing other article text! If so, it's possible the author and even the editors may not be at fault. The blame could be on the Ars publishers using LLMs to automate monetization processes downstream of editorial. Which might explain the non-standard vague retraction. If so, that would make for an even more newsworthy article that's directly within Ars' editorial focus.

In the case of hallucinated quotes, I think the more important aspect is to describe how this happened, whether the author is a regular contributor, how the editors missed it, and what steps are being taken to prevent it from happening in the future.

It's good to issue a correction, and in this case to retract the article. But it doesn't really give me confidence going forward, especially where this was flagged because the misquoted person raised the issue. It's not like Ars' own processes somehow unearthed this error.

It makes me think I should get in the habit of reading week-old Ars articles, whose errors would likely have been caught by early readers.

> It's not like Ars' own processes somehow unearthed this error.

It might be even worse (and more interesting) than that. I just posted a sister response outlining why I now suspect the fabrication may have actually been caused by Ars' own process. https://news.ycombinator.com/item?id=47027370. Hence, the odd non-standard retraction.

Yes I just read the retracted article and I can't find anything that I knew was false. What were the fabricated quotes?

This blog post from the person who was falsely quoted has screenshots and an archive link: https://theshamblog.com/an-ai-agent-published-a-hit-piece-on...

I was wondering the same thing. After I posted above, I followed the archive.org link to the original article and did a quick search on the last four quotes, which the article claims are from Scott's blog. None appear on the linked blog page. The first quote the article claims is from Scott does appear on the linked Github comments page.

When I wrote my post above, I hadn't yet read the original article on achive.org. Now that I know the article actually links to the claimed original sources on Scott's blog and Github for all the fabricated quotes, how this could have happened is even more puzzling. Now I think this may be much more interesting than just another case of "lazy reporter uses LLM to write article".

Ars appears to use an automated tool which adds text links to articles to increase traffic to any related articles already on Ars. If that tool is now LLM-based to allow auto-generating links based on concepts instead of just keywords, perhaps it mistakenly has unconstrained access to changing other article text! If so, it's possible the author and even the editors may not be at fault. The blame could be on the Ars publisher's using LLM's to automate monetization processes downstream of editorial. Which might explain the non-standard vague retraction. If so, that would make for an even more newsworthy article that's directly within Ars' editorial focus.

This is not a retraction. It is just CYA - Cover your Arse Technica.

They need to enumerate the specific details they fudged.

They need to correct any inaccuracies.

Otherwise, there is little reason to trust Arse Technica in the future.

Previously:

Ars Technica makes up quotes from Matplotlib maintainer; pulls story

https://news.ycombinator.com/item?id=47013059

Imagine a future news environment where oodles of different models are applied to fact check most stories from most major sources. The markup from each one is aggregated and viewable.

A lot of the results would be predictable partisan takes and add no value. But in a case like this where the whole conversation is public, the inclusion of fabricated quotes would become evident. Certain classes of errors would become lucid.

Ars Technica blames an over reliance on AI tools and that is obviously true. But there is a potential for this epistemic regression to be an early stage of spiral development, before we learn to leverage AI tools routinely to inspect every published assertion. And then use those results to surface false and controversial ones for human attention.

So, the solution to too much AI is... Even more AI! You sound like you would fit just right at a LLM-shop marketing department.

The author of the blog post hypothesised that the fabrication happened as a result of measures blocking LLMs from scraping their blog. If that is the case, adding more LLMs would not in fact accomplish anything at all.

Feels like nail in the coffin, Ars has already been going downhill for half a decade or more.

I unsubscribed (just the free rss) regardless of their retraction.

I see a lot of negative comments on this retraction about how they could have done it better. Things can always be done better but I think the important thing is that they did it at all. Too many 'news' outlets today just ignore their egregious errors, misrepresentations and outright lies and get away with it. I find it refreshing to see not just a correction, but a full retraction of this article. We need to encourage actual journalistic integrity when we see it, even if it is imperfect. This retraction gives me more faith in future articles from them since I know there is at least some editorial review, even if it isn't perfect.

Glib observation, but this sounds quite generic and AI-written.

Zero repercussions for the senior editor involved in fabricating quotations (they neglect to even name the culprit), so this is essentially an open confession that Ars has zero (really, negative) journalistic integrity and will continue to blatantly fabricate articles rather than even pretending to do journalism, so long as they don't get caught. To get to the stage where an editor who has been at the company for 14 years is allowed to publish fraudulent LLM output, which is both plagiarism (claiming the output as his own), and engaging in the spread of disinformation by fabricating stories wholesale, indicates a deep cultural rot within the organisation that should warrant a response deeper than "oopsie". The publication of that article was not an accident.

What is the evidence that lead you to believe there have been no repercussions? In what world do they retract the article without at a minimum giving a stern warning to the people involved?

If they had named the people involved, the criticism would be, "they aren't taking responsibility, they're passing the buck to these employees."

Who got fired?

The bylines are known, check in 4-5 months whether either or both names still appear on new articles or not..

They're both still on the staff page presently. https://arstechnica.com/staff-directory/

It is definitely not a good look for a "Senior AI Reporter."

This is a US holiday weekend and lots of people are going to be on weekend vacations. Check back on Wednesday.

Then they should take their time publishing this statement.

Nobody is in a hurry.

The lack of specificity to me suggests that someone probably is getting fired. It is written as if legal vetted every word.

> We have covered the risks of overreliance on AI tools for years

If the coverage of those risks brought us here, of what use was the coverage?

Another day, another instance of this. Everyone who warned that AI would be used lazily without the necessary fact-checking of the output is being proven right.

Sadly, five years from now this may not even result in an apology. People might roll their eyes at you for correcting a hallucination they way they do today if you point out a typo.

> Sadly, five years from now this may not even result in an apology. People might roll their eyes at you for correcting a hallucination they way they do today if you point out a typo.

I think this track is unavoidable. I hate it.

[dead]

tl;dr: We apologize for getting caught. Ars Subscriptors in the comments thank Ars for their diligence in handling an editorial fuckup that wasn't identified by Ars.

I don't know how you could possibly have that take away from reading this. They did a review of their context to confirm this was an isolated incident and reaffirmed that it did not follow the journalistic standards they have set for themselves.

They admit wrong doing here and point to multiple policy violations.

> That rule is not optional, and it was not followed here.

It’s not optional, but wasn’t followed, with zero repercussions.

Sounds optional.

Reading between the lines, this is corporate-speak for "this is a terminable offense for the employees involved." It's a holiday weekend in the US so they may need to wait for office staff to return to begin the process.

They might as well wait till business hours to sort things out before publishing a statement. Nobody needs to see such hollow corpo speak on a Sunday.

No, admitting fault as soon as possible makes a big difference. It's essential to restoring credibility.

If they had waited until Monday the thread would be filled with comments criticizing them for waiting that long.

https://arstechnica.com/civis/threads/um-what-happened-to-th...

> we probably won't have something to report back until next week.

The forum thread is locked.

Yeah, but the problem is that by not making it clear that additional actions may be coming, they're barely restoring credibility at all, because the current course of action (pulling the article and saying sorry) is like the bare minimal required to avoid being outright liars - a far cry from being credible journalists. All they've done is leave piles of readers (including Ars subscribers) going "wtf".

If they felt the need to post something in a hurry on the weekend, then the message should acknowledge that, and acknowledge that "investigation continues" or something like that

You don't announce that you're firing people or putting them on a PIP or something. Not only is it gauche but it makes it seem like you're not taking any accountability and putting it all in the employees involved. I assume their AI policy is fine and that the issue was it wasn't implemented/enforced, and I'm not sure what they can do about that other than discipline the people involved and reiterate the policy to everyone else.

What would you have liked to see them announce?

They just needed to expand "At this time, this appears to be an isolated incident." into "We are still investigating, however at this time, this appears to be an isolated incident". No additional details required.

And yes, it looks like Ars is still investigating (bluesky post by one of the authors of the retracted article) https://bsky.app/profile/kyleor.land/post/3mewdlloe7s2j

> It's a holiday weekend in the US so they may need to wait for office staff to return to begin the process.

That's not how it works. It's standard op nowadays to lock out terminated employees before they even walk in the door.

Sometimes they just snail mail the employee's personal possessions from their desk.

Moreover, Ars Technica publishes articles every day. Aside from this editor's note, they published one article today and three articles yesterday. So "holiday weekend" is practically irrelevant in this case.

> That's not how it works.

Some places.

> It's standard op nowadays to lock out terminated employees before they even walk in the door.

Some places.

You're speaking very authoritatively about what's "standard", in a way that strongly implies you think this is either the way absolutely everyone does it, or the way it should be done.

It's standard op nowadays to acknowledge that your experiences are not universal, and that different organizations operate differently.

> You're speaking very authoritatively about what's "standard", in a way that strongly implies you think this is either the way absolutely everyone does it, or the way it should be done.

Neither. I just meant it's common.

The comment I replied to said, "they may need to wait for office staff to return to begin the process."

I think the commonality of the practice shows that Ars Technica doesn't need to wait for office staff to return to begin the process, if office staff is even gone in the first place (again, Ars Technica appears to be open for business today). There's certainly no legal reason why they'd need to wait to fire people.

Does Ars Technica have a "policy" to only fire people on weekdays? I doubt it. Imagine reading that in the employee handbook.

Besides, President's Day is not a holiday that businesses necessarily close for. Indeed, many retailers are open and have specific President's Day sales.

> (again, Ars Technica appears to be open for business today). There's certainly no legal reason why they'd need to wait to fire people.

They normally aren't, they probably write the stories on the weekdays and prepare them to automatically publish over the weekend, with only a skeletal staff to moderate and repair the website. Legal, HR, and other office staff probably only work weekdays, or are contracted out to external firms.

Their CEO posted a quick note on their forums the other day about this which implied they don't normally work on holidays and it would take until Tuesday for a response.

> Their CEO posted a quick note on their forums the other day about this which implied they don't normally work on holidays and it would take until Tuesday for a response.

Judging from today's editors note, if things need to happen more quickly, then they do.

That's true of every executive position, but not necessarily for HR or legal. Especially if they use an external firm.

It's embarrassing for them to put out such a boilerplate "apology" but even more embarrassing to take it at its word.

It's such a cliche that they should have apologized in a human enough way that it didn't sound like the apology was AI generated as well. It's one way they could have earned back a small bit of credibility.

The comments are trending towards being more critical as of my posting. A lot more asking what they're going to do about the authors, and what the hell happened.

> Greatly appreciate this direct statement clarifying your standards, and yet another reason that I hope Ars can remain a strong example of quality journalism in a world where that is becoming hard to find

> Kudos to ARS for catching this and very publicly stating it.

> Thank you for upholding your journalistic standards. And a note to our current administration in DC - this is what transparency looks like.

> Thank you for upholding the standards of journalism we appreciate at ars!

> Thank you for your clarity and integrity on your correction. I am a long time reader and ardent supporter of Ars for exactly these reasons. Trust is so rare but also the bedrock of civilization. Thank you for taking it seriously in the age of mass produced lies.

> I like the decisive editorial action. No BS, just high human standards of integrity. That's another reason to stick with ARS over news feeds.

There is some criticism, but there is also quite a lot of incredible glazing.

Yeah, the initial comments are pretty glazey, but go to the second and third pages of comments (ars default sorts by time). I'll pull some quotes:

> If there is a thread for redundant comments, I think this is the one. I, too, will want to see substantially more followup here, ideally this week. My subscription is at stake.

> I know Aurich said that a statement would be coming next week, due to the weekend and a public holiday, so I appreciate that a first statement came earlier. [...] Personally, I would expect Ars to not work with the authors in the future

> (from Jim Salter, a former writer at Ars) That's good to hear. But frankly, this is still the kind of "isolated incident" that should be considered an immediate firing offense.

> Echoing others that I’m waiting to see if Ars properly and publicly reckons with what happened here before I hit the “cancel subscription” button

No reason to trust that the comment section is any more genuine than the deleted fake article. If an Ars employee used genAI to astroturf these comments, they clearly would not be fired for it or even called out by name.

[dead]