this post was submitted on 17 Nov 2026
1283 points (98.9% liked)
Microblog Memes
12613 readers
1790 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
RULES:
- Your post must be a screen capture of a microblog-type post that includes the UI of the site it came from, preferably also including the avatar and username of the original poster. Including relevant comments made to the original post is encouraged.
- Your post, included comments, or your title/comment should include some kind of commentary or remark on the subject of the screen capture. Your title must include at least one word relevant to your post.
- You are encouraged to provide a link back to the source of your screen capture in the body of your post.
- Current politics and news are allowed, but discouraged. There MUST be some kind of human commentary/reaction included (either by the original poster or you). Just news articles or headlines will be deleted.
- Doctored posts/images and AI are allowed, but discouraged. You MUST indicate this in your post (even if you didn't originally know). If an image is found to be fabricated or edited in any way and it is not properly labeled, it will be deleted.
- Absolutely no NSFL content.
- Be nice. Don't take anything personally. Take political debates to the appropriate communities. Take personal disagreements & arguments to private messages.
- No advertising, brand promotion, or guerrilla marketing.
RELATED COMMUNITIES:
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
While frequently true, the recent events seem to be more the opposite, deploying improvements to systems that weren't broken (yet).
The FAA? Upgrading to a new piece of network equipment. An act of finally working toward refreshing long neglected infrastructure.
Microsoft? Some developer pushed a windows os change in July, and circumstances fired off now to expose it as flawed.
Banking? Again, some developer at one bank pushing some change.
As to why all at once, could be coincidence, but if it isn't the likely connecting factor is AI. You need to create the complex configuration for a piece of network gear? What a pain, just feed Claude the current config and ask to port it to new equipment. Want some nebulous software improvement but don't have any ideas? Have Claude look for, provide a solution, and also have it "audit" and "test" its own solution. I have seen all of the above happen and go horribly wrong when I am actually in a position to intercept, but it is super popular.
Read a comment elsewhere that the banks aren't quite comfortable enough with AI to let it make the code. But, what they are doing, is using AI to hunt for vulnerabilities, and get people to patch them. And the AI are finding tons of holes, so there is pressure to push tons of updates to fix them, because if their AI can find them, then hackers' AI can find them. And so the workload has exploded with tasks labeled Priority 1, Critical! non-stop, resulting in sloppy updates.
That's 99% of what's happening,
Compounded by major governmental cybersecurity cuts over the past few administrations and a low-effort FAA update. (not to say the FAA update was lazy, but insufficiently designed/tested/handled)
Exactly this
It is very possible they became pressured to perform an upgrade because something on the old system was compromised and out of support.
Legacy stacks quite often maintain old tech, and then somewhere in there will be a library that has a critical exploit and has been totally replaced for future major versions.
Unsure if you're defending or objecting to the comment. Flawed and outdated code needs to be replaced and that pressure should be maintained. The 'Go Fast And Break Things' model works OK in an internal corporate environment, but not when we're talking about the FAA or banking. Outlook can fuck right off.
Outdated hardware needs to be replaced, but I'm with JJ about the likely root cause. Some boss decided that the cheapest way to fulfill their job/contract was to install or deploy whatever ChatGPT told them would work.
No it doesn't. Nuclear launch systems were running on floppy disks in the 2010s, IIRC, if it ain't broke then "fixing it" is at best a nice to have.
Now, if it's insecure then we should replace it. Unless you're replacing it with something even less secure (like AI, perhaps).
fair - not broken (yet) doesn't mean shouldn't be maintained, though.
Most solid state things are pretty much static, by definition, but there's still stuff like plastic dry rot or metal corrosion. We're talking decades, but we're also talking decades. If that critical router failed outright the result might have been worse while a replacement was sourced, with a follow-on failure when the code bombed too.
I'm not defending the outage -- there should have been better testing -- but I've been on the receiving end of a minimal but crucial server's power supply capacitor failing (the post-mortem was wild to figure out what broke). That server was ancient and should have been replaced before it failed and the fire drill to recover it (even just taking a backup and restoring to a VM) was unpleasant.
On the bank, a possibility, on Microsoft, based on what they detailed sounded like a go at performance optimization.
For security, I get it, there is little time to lose in this scenario, usually. But huge volume of changes for change's sake are also in play.