The point is that once they went public, they said they were gonna be removing certain horrible communities, and the particular community that particular video is on would have been like at the top of the list if I was in charge of Reddit.
But honestly I don’t give a flying fuck.
What trips me out is that somehow they still have the video of the dude that somehow survived after blowing his own face off with a shotgun. It’s fucked up, sad and sickening.
Honestly I would have just put him out of his misery if I had found him like that. And no, I will not be linking that video here or anywhere for that matter, it’s pure nightmare fuel.
Even so, do you actually understand the glitch and how it works?
If it’s not supported in the web browser port, that comment is a perfectly valid answer.
Dang LOL! Thanks for trying at least.
The real question is, does it support the item duplicating bug?
I write graphics software that almost seems intuitive, until you realize I gave it a split personality.
Even I forget about the split personality side of it.
All they gotta do is change their company name to avoid lawsuits. Anyone got any ideas for a new name for them?.. 🤔
ClusterFuck comes to mind…
Task failed successfully 👍
Kinda ironic that it’s called CrowdStrike, cuz it sure as hell struck a huge crowd of systems!
Well done CrowdStrike crew, maybe you guys will start testing your stuff before deploying to the public… 🤦♂️
Still, with billions of dollars in losses across the globe and all the various impacts it’s having on people’s lives, is nobody gonna be held accountable? Will they just end up charging CrowdStrike as a whole a measly little fine compared to the massive losses the event caused?
One of their developers goofed up pretty bad, but in a fairly simple and forgivable way. The real blame should go on the higher ups that decided that full proper testing wasn’t necessary before deployment.
So yes, they really need to review their policies and procedures before pressing that deploy button.
Indeed, I fully agree. They obviously neglected on testing before deployment. So you can split the blame between the developer that goofed on the null pointer dereferencing and the blank null file, and the higher ups that apparently decided that proper testing before deployment wasn’t necessary.
Ultimately, it still boils down to human error.
Watch the video that I linked as an edit from Dave Plummer, he explains it rather well. The driver was signed, it was the rolling update definition files from CrowdStrike that were unsigned.
Hey, why not just ask Dave Plummer, former Windows developer…
https://youtube.com/watch?v=wAzEJxOo1ts
When anywhere from 8.5 million to over a billion systems went down, numbers I’ve read so far vary significantly, still that’s way too much failure for a simple borked update to a kernel level driver, not even made by Microsoft.
If you were a developer that knew you were responsible for developing ring zero code, massively deployed across corporate systems across the world, then you should goddamned properly test the update before deploying it.
This isn’t a simple glitch like a calculation rounding error or some shit, the programmers of any ring zero code should be held fully responsible, for not properly reviewing and testing the code before deploying an update.
Edit: Why not just ask Dave Plummer, former Windows developer…
I hope this incident shines more light on the greedy rich CEOs and the corners they cut, the taxes they owe, the underpaid employees and understaffed facilities, and now probably some hefty fines, as just a slap on the wrist of course…
Your version of Florida looks funny…
I had a ColecoVision with the Atari 2600 adapter. Yes, they made an adapter for it.
A ColecoVision, with the Atari 2600 adapter.
It is said that the foreskin of Jesus still exists…
https://en.wikipedia.org/wiki/Holy_Prepuce
For all I know it could be just an ancient dried up piece of bacon 🤷♂️
Ouch. Good luck with that 🤞