Botched update leads to claims that competitors are "ambulance chasing."
  • Lexi Sneptaur@pawb.socialEnglish
    0·
    4 months ago

    They deserve to go bankrupt after that level of damage. I won’t be surprised if a class action comes against them for gross negligence within the next few years. They’re cooked and they know it.

  • Bosht@lemmy.worldEnglish
    0·
    4 months ago

    Yeah, it was an international fuck up. You’re going to get heat, and it’s 100 percent deserved. Go cry in a corner and fuck off into oblivion.

  • Boozilla@lemmy.worldEnglish
    0·
    4 months ago

    I wonder if they’ll end up doing a rename / rebrand if “ClownStrike” continues to haunt them (as it should).

    If they do, I’m sure the new name will be some focus tested aberration they pay way too much for.

  • Blaster M@lemmy.worldEnglish
    0·
    4 months ago

    Cry me a half billion dollar river, maybe we can use that money to fix all the damamges it did.

  • reginald_crunklebottom_III@lemmy.worldEnglish
    0·
    4 months ago

    Crowdstrike didn’t just fuck up, they killed people. I personally had to postpone a blood test, but mine wasn’t critical and I’m alive to complain. Not everyone is.

  • hark@lemmy.worldEnglish
    0·
    4 months ago

    Nothing shady about that commentary after seeing how they screwed up. I couldn’t believe how amateur hour the cause of the crash was (the program not validating definition file contents, which spectacularly failed when fed a file consisting only of zeroes). They should rename themselves to ClownTrike.

    • db2@lemmy.worldEnglish
      0·
      4 months ago

      That wasn’t what was in the file, it was actual stuff. I saved a copy of it.

      What happened was the file directed their craptastic snake oil software, which did absolutely no sanity checking first, to access memory it wasn’t actually given which predictably resulted in it crashing, and since its dick was way up the kernels butt at the time they both went down together.

      I’ve been calling them ClownStrike because they’re clowns and their incompetence struck everyone else hard.

      • aodhsishaj@lemmy.worldEnglish
        0·
        4 months ago

        Yup a null pointer reference for a boot time driver. Which Microsoft never should’ve signed and should revoke. But ya know… Money

      • hark@lemmy.worldEnglish
        0·
        4 months ago

        Ah, thanks for the clarification on the details. Either way it boggles my mind that they didn’t have checks in place.

  • JigglySackles@lemmy.worldEnglish
    0·
    4 months ago

    “Our industry is built on trust,” Sentonas said

    And instead of following that statement with an apology to all the companies and people they royally fucked in the ass with their shitty business practices, they instead whined about other people pointing out what a massive, colossal, and completely preventable fuckup this was.

    Good going sealing my resolve to never use crowdstrike.

  • ulkesh@lemmy.worldEnglish
    0·
    4 months ago

    Awww, let’s all feel bad for the rich, shitty company that has shitty quality control.

    • AdamEatsAss@lemmy.worldEnglish
      0·
      4 months ago

      Hey, they’re trying their hardest. It’s hard because they had the joke build stored right next to the actual build so when they went to push it they clicked the wrong one.

  • corsicanguppy@lemmy.caEnglish
    0·
    4 months ago

    We don’t blame the leopards for eating faces. We blame the morons who let an external entity have control over their devices. And a clowd one at that.

  • portuga@lemmy.worldEnglish
    0·
    4 months ago

    I just wish they made it a feature, or something, cause I really dislike working and stuff