3 ms·
The fun is really gonna start if the root cause of this somehow implicates an AI as a primary cause.
by Msurrow 1y ago
The fun is really gonna start if the root cause of this somehow implicates an AI as a primary cause.
- karel-3d 1y agoI haven't seen the "90% of our code is AI" nonsense from Amazon.
- gdulli 1y agoTheir business doesn't depend on selling AI so they have the luxury of not needing to be in on that grift.
- some_furry 1y agohttps://archive.is/b6aUD https://archive.is/b6aUD
- aurareturn 1y agoIt's never an AI's fault since it's up to a human to implement the AI and put in a process that prevents this stuff from happening. So blame humans even if an AI wrote some bad code.
- Msurrow 1y agoI agree but then again it’s always a humans fault in the end. So probably a root cause will have a bit more neuance. I was more thinking of the possible headlines and how that would potentially affect the public AI debate. Since this event is big enough to actually get the attention of eg risk management at not-insignificant orgs.
- xenocratus 1y ago> but then again it’s always a humans fault in the end Disagree, a human might be the cause/trigger, but the fault is pretty much always systemic. A whole lot of things has to happen for that last person to cause the problem.
- Msurrow 1y agoAlso agree. “What” build the system though? (Humans) Edit: and more important who governed the system, ie made decisions about maintainance, staffing, training, processes and so on
- deleted 1y ago[deleted]
- portaouflop 1y agoIt’s gonna be DNS
- WelcomeShorty 1y agoYour remark made me laugh, but..: "Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution." https://health.aws.amazon.com/health/status https://health.aws.amazon.com/health/status
- erpellan 1y agoIt’s always DNS! Except when it’s the firewall.
- blibble 1y agoif that's the case it'll be buried