• Pratai@piefed.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 days ago

    Good. The more thins shit happens the more people will rip relying on it and see it as the unreliable bullshit that it is.

  • Taasz/Woof@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 days ago

    No backups? Maybe I can understand not having full duplicates due to the cost, but surely it was on a system with at least snapshots in place or something right??

        • Elvith Ma'for@feddit.org
          link
          fedilink
          English
          arrow-up
          0
          ·
          14 days ago
          ~$ sudo eat -rm ./Homework
          
          @crank0271@lemmy.world is not in the sudoers file. This incident will be reported.
          

          sigh

          ~$ groups
          crank0271 docker
          
          ~$ docker run -rm -v ./Homework:/mnt/Homework --entrypoint '/bin/sh' alpine:latest -c 'sudo eat -rf /mnt/Homework'
          
          • Dave.@aussie.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            14 days ago

            ~$ groups crank0271 docker

            ~$ docker run -rm…

            No joke, this is exactly what LLMs will do if they can’t do something directly.

            • Elvith Ma'for@feddit.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              14 days ago

              This is why I told some colleagues several times to NOT put their user into the docker group AND to set the docker command for Claude at least to ‘ask every time’.

              That fucker circumvents your guardrails all the time. “Oh I’m not allowed to read a .env file with the harness? Let’s check cat .env!” Yesterday Claude even wrote a little python script to try to print the .env file, because he thought he’d need it to debug a container. (Spoiler - the problem wasn’t even with some env vars and also the .env was just filled with dummy values as it is an example from a public repository anyways).

  • eronth@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 days ago

    I would be so fucking mad if I worked on this and some producer just gave AI direct access to the only copy.

  • joey_builds@eviltoast.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    14 days ago

    Whatever the agent was actually doing, the real failure is that it had destructive write access to the only copy of finished work. That’s a permissions problem before it’s an AI problem — no automation, human or otherwise, should be able to hard-delete production assets without a human confirming the destructive step.

    The fact that the season is just gone also tells me there was no immutable backup or soft-delete tier behind it, which is rough for a broadcast workflow where the footage is irreplaceable. Agents are getting broad tool access by default right now, and this is the cautionary tale for giving them delete rights alongside read rights.

  • VibeSurgeon@piefed.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    The article plainly states that the production company says it wasn’t AI, but instead that it was human error that led to the data loss.

    The AI-thing was merely a rumour.

    • Weep@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      15 days ago

      they say specifically “inte är en ”AI-agent som agerat självständigt”” (double quote). which translate to an "not an “AI agent which acted independently”. so depending if that counts as human error or not… still up to to debate. It probably was AI, just not someone shift+delete the wrong folder.

      I do however blame the backup crew which definitely should’ve had their backups in place.

    • frongt@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      15 days ago

      Humans run AI. Even if it was deleted by AI, it’s still the responsibility of the person running it.

      • kewjo@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        14 days ago

        i would say it’s the fault of whoever thought it was a good idea to hook it up to their data. the workers are just doing what they’re paid to do and trying to put up with literal insanity or risk termination.

        • Railcar8095@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          14 days ago

          I blame the one who should have set the backups. Even if it was deleted by a malicious actor, they there’s no excuse to not have backups

  • EowynCarter@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    14 days ago

    I wonder how many similar stuff need to happens before people realize they still need to keep their brains on when using AI and know what they’re doing.