• @Z3k3
      link
      English
      352 months ago

      I’ll be honest I thought it was just this one recaptioned. Thank you for pointing it out that they are messing around in different ways

      • @[email protected]
        link
        fedilink
        English
        172 months ago

        “We were going to try swordfighting, but all my compiling is on hold.” Is the alt text. I thought it was the same too.

    • @RustyNova
      link
      English
      142 months ago

      I even thought about a crowd strike version of #303 today too

  • Track_Shovel
    link
    fedilink
    English
    462 months ago

    Pretty much what happens when you knock out something important

  • @[email protected]
    link
    fedilink
    English
    42
    edit-2
    2 months ago

    Me, the only sysadmin with access to the data center and AD: “I’m drowning!”

    ISR team that selected Crowdstrike: " were going to the coffee shop, let us know when it’s back up"

    Today has been a nightmare of stupid problems

    • @RunningInRVA
      link
      English
      162 months ago

      I hope you guys run a lessons learned after it all. Go ahead and roll your eyes, but reflecting on prior performance can have a huge impact for the future. It shouldn’t all come down to you in the end, and that’s okay.

      • @[email protected]
        link
        fedilink
        English
        11
        edit-2
        2 months ago

        Every org worth their weight will be doing a root cause analysis after this. So many lessons learned. We were impacted very minimally and only through external vendors.