• Ashtear@piefed.social
      link
      fedilink
      English
      arrow-up
      24
      ·
      3 months ago

      Well, I can see how that could happen, and in fact, copy-paste artifacts and unintended summaries/hallucinations have happened to me when grabbing output back from an LLM.

      Here’s the thing though: I catch it 100% of the time because my writing has version control and I compare diffs. When dealing with something that can exist as plain text, there isn’t a good reason not to have that setup. I’m no journalist, but it blows my mind that writers who deal specifically in reported facts apparently don’t have systems in place to idiot-proof and preserve their sources of truth.

      I get it, at some point back in the analog days there were more editors and copywriters that actually verified these things, and those jobs were sacrificed at the altar of capitalism. I’ve seen writing quality on the web take a downturn as a result. But for fuck’s sake y’all, maybe do the bare minimum and start implementing safeguards before you let your writers use inherently lossy tools?

    • artyom@piefed.social
      link
      fedilink
      English
      arrow-up
      18
      ·
      3 months ago

      Thank fuck Bsky has these character limits or else he would have had to put all that text in an easily legible format for reading and copying. Fuck character limits up their stupid asses.

    • LukeZaz@beehaw.org
      link
      fedilink
      English
      arrow-up
      14
      ·
      edit-2
      3 months ago

      This is a good way to handle the situation and an understandable and believable scenario, so I’m perfectly willing to forgive this. I’m a little less okay with an apparent “work in spite of illness” policy, however.

      But still, it’s a serious blunder, and it needs to be said that any repeat of this at all would be very damning. I can’t forgive this level of fuckup twice. Any AI use is a risk, folks; treat it like one.

      • James R Kirk@startrek.websiteOP
        link
        fedilink
        English
        arrow-up
        10
        ·
        3 months ago

        When I first became aware of it, I did not expect this story to become a good case for worker’s rights and ensuring everyone has enough rest but here we are.

    • kibiz0r@midwest.social
      link
      fedilink
      English
      arrow-up
      12
      ·
      edit-2
      3 months ago

      This sounds eerily familiar…

      I don’t know if Hearst told him to use a chatbot to generate their “Best of Summer Lists,” but it doesn’t matter. When you give a freelancer an assignment to turn around ten summer lists on a short timescale, everyone understands that his job isn’t to write those lists, it’s to supervise a chatbot.

      But his job wasn’t even to supervise the chatbot adequately (single-handedly fact-checking 10 lists of 15 items is a long, labor-intensive pro­cess). Rather, it was to take the blame for the factual inaccuracies in those lists. He was, in the phrasing of Dan Davies, “an accountability sink” (or as Madeleine Clare Elish puts it, a “moral crumple zone”).

      https://locusmag.com/feature/commentary-cory-doctorow-reverse-centaurs/

    • XLE@piefed.social
      link
      fedilink
      English
      arrow-up
      10
      ·
      3 months ago

      Why would he play with an AI toy while he’s doing his job and he’s sick?

      Of course something was bound to happen.

  • artyom@piefed.social
    link
    fedilink
    English
    arrow-up
    19
    ·
    3 months ago

    On Friday afternoon, Ars Technica published an article containing fabricated quotations generated by an AI tool and attributed to a source who did not say them. That is a serious failure of our standards. Direct quotations must always reflect what a source actually said.

    That this happened at Ars is especially distressing. We have covered the risks of overreliance on AI tools for years, and our written policy reflects those concerns. In this case, fabricated quotations were published in a manner inconsistent with that policy. We have reviewed recent work and have not identified additional issues. At this time, this appears to be an isolated incident.

    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.

    We regret this failure and apologize to our readers. We have also apologized to Mr. Scott Shambaugh, who was falsely quoted.

    Nothing about who put it in there or what you’re doing to them?

    • Otter@lemmy.ca
      link
      fedilink
      arrow-up
      10
      ·
      3 months ago

      We are reinforcing our editorial standards following this incident.

      It sounds like they will be reminding their team not to do that and scrutinizing articles in the near future

      • artyom@piefed.social
        link
        fedilink
        English
        arrow-up
        8
        ·
        edit-2
        3 months ago

        Someone deserves to be fired. Just imagine you’re paying someone to do a job and they just 100% completely outsource it to a machine in 5 seconds and then goes home.

        • Totally Human Emdash User@piefed.blahaj.zone
          link
          fedilink
          English
          arrow-up
          12
          ·
          3 months ago

          He wrote the article himself, he just got mixed up when experimenting with using an AI tool to help him extract quotes from a blog entry. (He is the head AI writer, so learning about these tools is his job.) It was nonetheless his failure to check the quotes he was copying from his note to make sure that he got them right… but an important bit of context is that he had COVID while doing all this. Now, arguably he should have taken sick time off instead of trying to work through it (as he admits), but this would have cost him vacation time, and the fact that he even was forced into making this choice is a systemic problem that is not being sufficiently acknowledged.

        • Assassassin@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          4
          ·
          3 months ago

          So you’re calling for someone to be fired without actually reading the article or understanding the situation? What punishment do you deserve for your laziness?

  • sgibson5150@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    6
    ·
    3 months ago

    I read them regularly for years until they started banning folk in the forums for pointing out how problematic it is for Eric Berger to still be slobbering on Elon’s knob.

    Don’t think I’m missing much, though I do miss Beth Mole.

    • TheRtRevKaiser@beehaw.orgM
      link
      fedilink
      arrow-up
      5
      ·
      3 months ago

      For the most part, the comments I have removed on this thread have been removed for violating Beehaw’s only rule: Be(e) Nice.

      I have zero problem with people criticizing this journalist. I do have a problem with users attacking one another or using misogynist language (it’s possible in that case there’s a cultural disconnect. I’m from the US, where “cunt” is a pretty serious gendered insult. I know it’s not considered as big of a deal in other english speaking places, but frankly I’ve been getting enough reports on this thread that I’m getting a bit sick of dealing with it in general)

  • skip0110@lemmy.zip
    link
    fedilink
    arrow-up
    4
    ·
    3 months ago

    I think, all things considered, they handled this pretty well, and I’m actually more likely now to read an Ars article than before the article (when I had a neutral opinion).

  • Powderhorn@beehaw.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 months ago

    It is 23.43, and I can’t analyze this tonight. Ars has been good for a long while, and I enjoy their reporting. To have to reassess this is disappointing, but I’ve already had to feel this with the NYT and WaPo. Not exactly a huge loss here. But I want to fully investigate what happened ahead of reaching a conclusion.

    Rest assured, I will reach a conclusion. I don’t think I’ll like the one I think I’ll find, but that’s journalism for you. I will withhold judgment until I’ve had a chance to fully examine what happened here.

    • Helix 🧬@feddit.org
      link
      fedilink
      English
      arrow-up
      13
      ·
      3 months ago

      Why write this comment when you don’t have anything to say? I’m puzzled why I should care that you did not analyse this yet.

      • Powderhorn@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        There is no reason for you to care. I am informing users familiar with my writing and methods that this is now on my radar, but I can’t yet do it justice. I’m being honest about not being ready to perform analysis.

        • Helix 🧬@feddit.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          Ah so you’re important and have followers waiting what you have to say and you don’t want to keep them in the dark about your schedule?

          Sorry, I didn’t want to disturb a Main Character. Thank you for your kind response.