@mttaggart
"But that person has not come forward. If they instructed the agent to generate the blog post, they bear responsibility for a personal attack on a volunteer maintainer. "
Sounds like a solid case of #Libel to me

@mttaggart Sounds like the editors @ArsTechnica are letting their #AIAgent 's run rampant as well.

@mttaggart@infosec.exchange ​​

@mttaggart @catsalad
slop on slop action 🫦 send toot

@tehfishman @catsalad Where do you think you are, Moltbook?

@mttaggart LMAO. I'm glad I ditched @arstechnica a little bit ago when their reporting got way too breathlessly credulous about AI bullshit. At least they're experiencing the consequences of their own shoddy reporting.

@mttaggart @catsalad Moltbook is like a back and forth forever with the same slop situation ))><((

@mttaggart that's certainly one way to end their journalistic career. what else has benj and kyle been fabricating? this stuff is never a one-off. it was just brazen enough this time which means they just got eh, sloppy.

@datarama@hachyderm.io @mttaggart@infosec.exchange Same. That fucker has been trying to push generative AI so hard using Ars' platform. But has managed to just barely toe the line.

He finally slipped up hard.

@mttaggart A 404 without an apology is a terrible look for them. In my life you get one shot. If you slop me once I will never use your service again...

@mttaggart thanks for documenting this. I've referenced your thread here

@implementcontrols @mttaggart it is a friday evening before a long weekend in the US, I'm giving it until tuesday

@cR0w

WILD! Thank you @mttaggart for reporting on this!

❝Okay, an update:

We have pulled the story over concerns that it may have gone against our content policies. I locked the comments, and I'm going to lock this one too, we need some time.

We are doing an investigation right now to figure out exactly what happened. Given that it's Friday afternoon we probably won't have something to report back until Monday, but we will follow up with an explanation for our readers. Edit: Monday is a holiday, my bad, and I don't know what we'll be able to say, so I don't want to over-promise anything.❞

Source: Ars forum https://arstechnica.com/civis/threads/journalistic-standards.1511650/#post-44249741

@Sobex @bnys @mttaggart Oh, you see the comment where Aurich called Discord demanding biometrics and scans of ID cards 'a nothingburger'? And the further comments (plural) where he defended that wording?

@mttaggart

We need some time to 'investigate' whether we are using AI or not. We plumb forgot.

LOL

@mttaggart I am shocked, shocked that an article under the name of Ars' resident bot licker contains hallucinations.

@implementcontrols They issued this statement:

@megatronicthronbanks

We have pulled the story over concerns that it may have gone against our content policies. I locked the comments, and I'm going to lock this one too, we need some time.

We are doing an investigation right now to figure out exactly what happened. Given that it's Friday afternoon we probably won't have something to report back until Monday, but we will follow up with an explanation for our readers. Edit: Monday is a holiday, my bad, and I don't know what we'll be able to say, so I don't want to over-promise anything.

Wait until we learn the results (or lack thereof) of this investigation.
Maybe its just CYA, maybe they are seriously looking into this.

@colo_lee What anti-trans piece?

@dusk @cR0w @mttaggart @iampytest1

"…I don't know what we'll be able to say, so I don't want to over-promise anything…"

You say, 'We won't use AI to write our publication'

There's nothing else to say.
There's no promises to be made.

Ars prides itself on technical accuracy. AI slop is a direct hit to their identity. The longer they wait to give a straight answer, the more it *appears* like they're trying to figure out how much they can get away with, instead of just being bluntly transparent.