this post was submitted on 18 Nov 2026
502 points (93.9% liked)
Fuck AI
8848 readers
1070 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
Rules:
- Relevant posts only.
- No bigotry.
- No misinformation.
- No NSFW/NSFL content without being labeled NSFW or being in an appropriately-labeled spoiler tag.
- This isn't a place to talk about the cons and (supposed) pros of AI for different use cases. This is /c/fuck_ai .
- Especially no AI advocacy.
- No AI-generated content. If you want to post examples of AI failing hillariously, there are other communities for that like !ArtificialIgnorance@lemmy.ca .
- Venting is part of the purpose of this community, but don't aim frustration or accusations at other users.
- These rules are a living document that may change in the future.
You can help the mod team by making your reports detailed.
Effective reports:
- "The third image is a well-known anti-semitic trope"
- "Claiming that 'agentic AI' can outperform humans at all jobs is misinformation"
Less effective reports:
- "Breaks rules"
- "Misinformation"
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm sure this will be hated here but no where in this article does it state AI caused the outage. It said the vulnerabilities were found using AI, but never specifies how the patches were created/reviewed. So we are just assuming since the patches were large that they used AI to generate them without significant review where someone said "this might be to large to push during business hours"
It's possible that the weakness was AI discovered but human remediated, but so far if an org is enthusiastic enough about AI identifying vulnerabilities in their systems, they are likely to be inclined to take in the suggested remediation.
You generally don't run these tools without getting a suggested remediation to go with the discovery.
There's gonna be stories decades later about a relatively small group of underpaid, overworked techs that thanklessly kept everyone safe from AI vulnerabilities just like they all raced to patch the Y2K stuff and no one really noticed.
It seems that it's not about the patches themselves but about the act of patching. All of this constant patching seems to bring other problems and that's what we're seeing.
Yeah, in my opinion we are seeing companies not testing the patches in test environments seeing how they act and releasing beta test versions to the companies that rely on the software to be able to test and fix their own software to ensure it works. That to me is all oversight and management issues. Whether you have 1 patch or 12, they all should have the same approval processes, if anything grouping the 12 together and implementing in a test environment, then making that beta available to the companies you sell the product too.
If the security flaw was so bad that they need to implement something now without prior testing they should have made a public announcement that the systems were being taken down for emergency maintenance to ensure the security of their, and their customers data. Which no company would want to do, thus they would have to decide which patches are actual high level risks, and how to get them tested outside the live version.
I've been getting wary of futurism articles, they seem to really distort the truth to say what we want to hear, not dissimilar to conservative misinformation sources
Nearly every news site that gets posted on social media is like this. Including lemmy. Most of the accounts posting links here are bots anyway.
It's in the same idea as citogenesis.
#1 Social media users have a fact that they want hear.
#2 A news site publishes a distorted article about that fact.
#3 Social media users check news for that fact and repost it.
#4 Now other news sites have sources. They publish their own articles about that fact, citing the article and social media.
. It's especially problematic about elections and AI. With elections it's about polling and voter sentiment. None of them are trying to report on reality. They're publishing whatever they think viewers want to see. That may have some overlap with reality, but it's not reality.
Same here. This is one of several articles where the headline was not only missleading, but outright wrong. I am critical of AI and all, but i don't want my worldview reinforced for the price of truth. I do not consider futurism a valid source any longer.
Al found "vulnerabilities"...vibe coder who replaced senior dev. Patches with vibe code from AI.
Yes, AI caused this shit.
Because it originally started with doge and there are no smart people in the room to not use AI. Do you seriously think this admin could do anything on their own? They of course, used AI.
FAA union president says DOGE fired essential employees without assessment
A new report looks at what the DOGE cuts actually cost the public
The frightening thing is that scenario is the most plausible one, given the short but catastrophic history of AI.
My thoughts are that it's poor management and no oversight. As an example if we look at say the PHP vulnerabilities found. Those flaws were found using AI from what we've been told. Companies like Cloudflare went out and developed patches and advised companies/users on how they could implement them to ensure the vulnerabilities were covered. A company/user then would need to review/run those patches in a test environment and see how it acts within their environment. What breaks, how much load it puts on the system.. what steps will be needed to update it to work with their environment, if none then verifying it works, setting a schedule and deploying a beta version of their companies products to the companies that relies heavily on them telling them when they will go live.
Those companies/users are then responsible for doing the same.
If someone vibe coding just pushed patches that took services across the nation down for a large number of users without notice, we should see JPMorgan and such filing lawsuits for breaching contacts/terms of use.
I'm not a coder, but after working IT related fields for 15+ years, someone writing a patch doesn't just get a greenlight by their manager, then their managers VP, or however they have there company structured.
Now if this was your home based projects you use for yourself or maybe family/friends... Sure. Someone could easily just push patches and have no one to answer too.
Well, look, people's actually that stupid, and AI boosters are too rich to market people into doing that. If people are giving their agents full control even in production cases/environments, then that's more than expected to happen. They're already vibecoding everything. Look at Proton i.e.
Worst part is that they're not shameful about doing so.
‘It wasn’t caused by US using AI, it was caused by OTHER PEOPLE using AI!’ Is a meaningless distinction if you’re trying to determine whether the rise in the use of AI (LLMs) is to blame.
Also, nowhere in this article, nor in the thin article linked, says anything about the Chase outage, AI or otherwise.
All ya gotta post is "AI BAD!" and lemmy stands up and barks like trained seals. 🦭⚽