Live data from Hacker News

Ars Technica fires reporter after AI controversy involving fabricated quotes

futurism.com

311–320 of 409 posts

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#311

Earlier quoted context omitted.

I'm sad to see them fire him. I've seen far worse: I have always approached issues by asking for accountability and improvement. Frankly, he already did: he openly apologised. I was very happy with that, it demonstrated integrity and I remained respecting him. Even worse, > I have been sick in bed with a high fever and unable to reliably address it (still am sick) [0] In an earlier HN thread, I saw someone ask why Ar…

Ars has probably the most rabid anti-AI audience of all the tech publications

Nah, The Register is far more strongly anti-AI. Mention AI and systemd in the same article and watch them froth

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#312

I guess Blameless Postmortems haven't arrived in journalism yet. Pretty weird that journalism as a business still revolves around "we hired a guy to write a thing, and he's perfect. oh wait, he's not perfect? it was all his fault. we've hired a new perfect guy, so everything's good now." My dudes... there are many ways you can vet information before publishing it. I get that the business is all about "being first", b…

[deleted]

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#313
post #169

Earlier quoted context omitted.

> the article doesn't include any facts that indicate this. It does include two facts: 1. That the reporter's bio on the webpage changed "...is a reporter at Ars " to "...was a reporter at Ars ". On the one hand, that's pretty thin sauce. On the other hand, that's not exactly the sort of change that gets made randomly. 2. They reached out to the various people involved, and although nobody has confirmed it, it's also…

IANAL, but those facts could support "fired", or "resigned", or "short-term contract not renewed", or probably other stuff.

I mean fired and resigned when it became clear you'd be fired are the same thing really.

We're not actually entitled to know the exact details of someone's job ending. They worked there. Now they don't. That much is the bit we're entitled to.

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#314

Earlier quoted context omitted.

It is not a job of the editor to assume that the author is lying to you. > This was an institutional error, not an individual reporter's fault. Ah yes, "the system made me use AI".

If the Ars Technica editorial process requires assuming reporters don't fabricate quotes, then their process is inadequate. That's like a software company letting junior engineers release directly to production with just a spellcheck and no real process to catch errors. Major publications like The New Yorker, The Atlantic, etc. have a dedicated fact-checking department that is part of the process and needs to give th…

> That's like a software company letting junior engineers release directly to production

This person wasn’t a junior.

Editorial processes don’t actually check every single line of everything that is written. Journalists are trusted to report accurately. This person demonstrated they could not be trusted.

> Why wasn't there any fact checking?

Why do programmers ever let any bugs get to production if they have code review? Journalistic outlets do not fact check literally every line that is ever written before it goes to publication.

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#315

Earlier quoted context omitted.

> The author himself fell on his sword in detail on Bluesky. Not exactly. He wrote a long excuse blaming being sick, sidestepping the issue that he was using AI tools to write for him and not making an effort to fact check. Also Bluesky is not Ars Technica. It doesn’t matter what he posts on his own obscure social media page. We’re talking about the journalistic platform where he was given a wide audience. > Your onl…

Maybe I don't understand journalism but this guy being a reporter, shouldn't he have had an editor reviewing his work before they hit publish? I understand trusting a senior reporter but I would think due to libel concerns, they would check people's quotes ESPECIALLY if the reporter was sick. Honestly it seems like journalism has been in their 'vibe code' era for a decade where they just publish whatever typos and al…

> Maybe I don't understand journalism but this guy being a reporter, shouldn't he have had an editor reviewing his work before they hit publish?

While the journalist is still responsible for their own actions, I agree with you that this being published in the first place is indicative of a deeper failure akin to - "if a junior dev accidentally deletes your production db on their first day that's on the company itself"

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#316

Earlier quoted context omitted.

Maybe I don't understand journalism but this guy being a reporter, shouldn't he have had an editor reviewing his work before they hit publish? I understand trusting a senior reporter but I would think due to libel concerns, they would check people's quotes ESPECIALLY if the reporter was sick. Honestly it seems like journalism has been in their 'vibe code' era for a decade where they just publish whatever typos and al…

It is not a job of the editor to assume that the author is lying to you. > This was an institutional error, not an individual reporter's fault. Ah yes, "the system made me use AI".

As someone who worked as a newspaper copy editor for the first third of my career, "assume that the author is lying to you" was the entire job.

A lapse in that non-hypothetically left me responsible, and legally liable, in situations like this.

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#317

Earlier quoted context omitted.

Maybe I don't understand journalism but this guy being a reporter, shouldn't he have had an editor reviewing his work before they hit publish? I understand trusting a senior reporter but I would think due to libel concerns, they would check people's quotes ESPECIALLY if the reporter was sick. Honestly it seems like journalism has been in their 'vibe code' era for a decade where they just publish whatever typos and al…

> Maybe I don't understand journalism but this guy being a reporter, shouldn't he have had an editor reviewing his work before they hit publish? While the journalist is still responsible for their own actions, I agree with you that this being published in the first place is indicative of a deeper failure akin to - "if a junior dev accidentally deletes your production db on their first day that's on the company itself…

> failure akin to - "if a junior dev accidentally

This person was not a junior.

He chose to use the AI tools knowing that they hallucinate.

The comparisons to an untrained junior are illogical. This person was a long time reporter who knew better.

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#318
post #26

I have a story with Benji. Last year I went viral, and Benji was the first person to interview me. It was a really cool experience, we chatted via Twitter dms, and he wrote a piece about my work - overall did a decent job. Then, 6 months later a separate project I was adjacent to was starting to pick up steam. I reached out to him asking if he wanted to cover us. No response. Then, tech crunch wrote an article on our…

> Then, 6 months later a separate project I was adjacent to was starting to pick up steam. I reached out to him asking if he wanted to cover us. No response. [...] > I reached to Benji again saying "Hey would you like to chat again, now we have some coverage?" And he finally responded, but said he couldn't report on me because he had a directive that he could only report on things that didn't have any prior or pre-ex…

If simply saying "Hi, would you be interested in covering this?" characterizes me as an annoying hustler then you know what I'll take it.

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#319
post #318

Earlier quoted context omitted.

> Then, 6 months later a separate project I was adjacent to was starting to pick up steam. I reached out to him asking if he wanted to cover us. No response. [...] > I reached to Benji again saying "Hey would you like to chat again, now we have some coverage?" And he finally responded, but said he couldn't report on me because he had a directive that he could only report on things that didn't have any prior or pre-ex…

If simply saying "Hi, would you be interested in covering this?" characterizes me as an annoying hustler then you know what I'll take it.

I'm not hustling enough to be honest.

Re: Ars Technica fires reporter after AI controversy involving fabricated quotes

#320

Earlier quoted context omitted.

> Maybe I don't understand journalism but this guy being a reporter, shouldn't he have had an editor reviewing his work before they hit publish? While the journalist is still responsible for their own actions, I agree with you that this being published in the first place is indicative of a deeper failure akin to - "if a junior dev accidentally deletes your production db on their first day that's on the company itself…

> failure akin to - "if a junior dev accidentally This person was not a junior. He chose to use the AI tools knowing that they hallucinate. The comparisons to an untrained junior are illogical. This person was a long time reporter who knew better.

Even a senior dev being able to unilaterally delete your prod entirely should not be possible.

But I don't think the intention was to compare with junior devs, its just a popular shorthand for "your process sucks".

Post reply on HN