Comment on Ars Technica Fires Reporter Over AI-Generated Quotes
limer@lemmy.ml 8 hours ago
Live by the sword 🗡️, die by the sword
Comment on Ars Technica Fires Reporter Over AI-Generated Quotes
limer@lemmy.ml 8 hours ago
Live by the sword 🗡️, die by the sword
AngryishHumanoid@lemmy.world 8 hours ago
You should read the guy’s explanation. It legitimately seems like an honest mistake, but given his work was specifically geared towards avoiding a situation like that I’m not surprised he was let go.
XLE@piefed.social 23 minutes ago
Ars saw his old explanation and conducted an internal review that took weeks, and found it lacking. His new explanation is… He isn’t giving one, after being asked for comment.
Greddan@feddit.org 8 hours ago
The guy had several explanations rolled into one so it seems more like a dishonest lie than an honest mistake. The guy the article was about had a decent explanation of how it happened though. His blog has AI scraping protections enabled, so when the so called journalist asked an AI to write an article for him citing the blog post, the AI couldn’t access it, and did what AI do, made shit up.
0x0@lemmy.zip 2 hours ago
Tell me more.
hexagonwin@lemmy.today 5 hours ago
lmao, didn’t know the ‘ai’ tool is that stupid to not handle website blocks/exceptions…
deadbeef79000@lemmy.nz 5 hours ago
It’s not quite like that. The tools used to scrape the web for training data couldn’t access the site to stacks the data, so it’s not encoded in the model.
The query interface for the model just hallucinates when there’s a ‘vacuum’.