←
ophello58,130 posts
ophello avatar

ophello

@ophello

Humanity should not tolerate the activity of NHI who operate on our home planet without our awareness or consent. ophello.github.io

◷ Joined March 2014▧ 2,867 Photos and videos
ophello avatar
ophello@ophello·Sep 4

No turning back now… My first on-camera interview is here. If you’re looking for a deep dive on NHI, the ethics of contact, and the challenge it poses to humanity, strap in for a 2-hour discussion on The Agenda Podcast UK with Alex Page!

It’s here — my interview with Ophello is live right now. An intense, detailed conversation you’ll want to hear. Head over to The Agenda Podcast UK and watch the full episode. Subscribe - youtube.com/@alexthepage youtu.be/-fwFkbYK6aU?si… #uap #ufo #alienabduction #ufotwitter

0:32
ophello avatar
ophello@ophello·17h

Update: this is what happened.

A way to think about these outages: AI is finding software vulnerabilities at breakneck speed. Alerts are going out to IT teams telling them they have to upgrade stuff or face dire consequences. They have two options, either upgrade software immediately, or take it offline to buy them more time. Not all upgrades and patches can be applied without breaking things, but it’s not always clear what may break. They are then left to make a snap decision: upgrade, possibly face failures, or punt? Any one of those could lead to outages and failures. The reason this is all happening at once is because IT managers are being forced to make these decisions all at once. So yes, this is caused by AI, but mostly indirectly: the real outages are being caused by security hardening and preventive maintenance.

ophello avatar
ophello@ophello·17h

The only thing more naive than thinking the government only tells the truth… is thinking that the government only lies.

ophello avatar
ophello@ophello·17h

This is what happened.

A way to think about these outages: AI is finding software vulnerabilities at breakneck speed. Alerts are going out to IT teams telling them they have to upgrade stuff or face dire consequences. They have two options, either upgrade software immediately, or take it offline to buy them more time. Not all upgrades and patches can be applied without breaking things, but it’s not always clear what may break. They are then left to make a snap decision: upgrade, possibly face failures, or punt? Any one of those could lead to outages and failures. The reason this is all happening at once is because IT managers are being forced to make these decisions all at once. So yes, this is caused by AI, but mostly indirectly: the real outages are being caused by security hardening and preventive maintenance.

ophello avatar
ophello@ophello·18h

A salient point on an ever increasing space of AI problems.

I haven’t lived here in awhile, but I see no other way to answer the hundreds of texts/DMs asking me if the world is, indeed, ending. In the span of six days, we’ve experienced; 11/12 — Microsoft outage 11/13 — Nationwide FAA ground stop 11/16 — Major US banking disruptions 11/17 — NSA’s classified internal network goes down We need far more analysis of why so much is breaking at once. I don’t want to get out over my skis here, and what I am hearing does not contradict the messaging that most of this is the result of screwy updates. But stepping back, the dots are starting to form a collective picture. We are seeing: • An explosion in severe and critical vulnerabilities, with AI accelerating discovery to 3X the number of vulnerabilities discovered in the same period last year. This is collectively being referred to as “vulnageddon” or “the vulnpocalypse.” • Mean time to exploit those vulnerabilities has collapsed to NEGATIVE SEVEN DAYS. AI allows attackers to find/exploit vulns far faster than software makers have time to fix them. • Powerful AI-enabled offensive tools like ARTEX have been thrown into the hands of every third tier nation state, cybercriminal and digital arsonist, which logically creates havoc. • This creates enormous pressure to compress patching windows and accelerate software updates, increasing the likelihood these fixes break things in unexpected, cascading ways. • Pressure to just “AI everything” means we are rolling out automated AI tooling on top of brittle infrastructure that can’t support it. My generation grew up in an extraordinary period of technological stability. We worked our way up the software stack, abstracting away layer after layer, until we lost a fundamental understanding of how the underlying systems actually work. We were told to “move fast and break things.” VCS told us to celebrate the idea that “software would eat the world.” Now we’re telling ourselves we can simply “roll out AI” across everything, as though nothing underneath will buckle. We never stopped to ask: SHOULD WE? Should we be digitizing every last nook and cranny of our companies, infrastructure, healthcare, homes, cars, bodies, lives? Especially when the complexity, interdependence, and fragility we were introducing overwhelmed our ability to understand/secure/maintain the systems we built? Nobody every asked: What if, in the name of progress, we were creating the ripest attack surface in human history? We are now entirely dependent on software systems that almost nobody understands end to end, that increasingly few people can repair, and that attackers can now probe at machine speed. We are hearing that incident response firms, the 911 for breach victims, are backlogged six months. Even those paid on retainer lack the bandwidth to triage every incident. The cavalry is disappearing. We are entering a period of unprecedented technological instability. “Software Beirut” is an incredibly apt analogy. We are in for a period of cascading failures, whether triggered by attackers, bad updates, or our own accumulated complexity. This, I’m sorry to say, is just the opening chapter.

ophello avatar
⟳ ophello retweeted
ophello@ophello·18h

You were just given the best and most coherent explanation for what just happened. And you shrug it off because it’s not entertaining or interesting enough. It doesn’t tickle your conspiracy brain. It’s boring. Well, tough. Life is often boring and disappointing.

ophello avatar
ophello@ophello·18h

This is what happened, folks. Tinfoil hats off.

It’s extremely obvious what is happening, I don’t know why we don’t just say it: Agents have made every system on earth highly vulnerable overnight, and there are swarms of agents attacking everyone. Everyone is running agents to defend themselves, creating rapid patching of security vulnerabilities in every system on earth. Orgs are either choosing to take their networks down during this transition, or the rapid AI-driven patches are sometimes causing mistakes and errors. They should just say what is happening. This is what every IT team on earth is dealing with.

ophello avatar
ophello@ophello·19h

WHEW! I knew we’d get there. This explains everything: the timing, the different types of systems, and the companies that were affected. We rushed to fix things AI told us to fix. We moved too fast and broke stuff.

We are now in the permanent cybersecurity time scramble There can be no further doubt that internal frontier AI model swarms are now capable of crippling entire economies with cyberattacks

Post attachment
ophello avatar
ophello@ophello·19h

This premise makes more sense than any other explanation I’ve seen for these disruptions. Common cause? Yes, in a way. But not a common problem. It explains the timing as well.

NEWS: Wall Street execs and NSA have told Congress that outages were caused by patching vulnerabilities identified by AI models, sources say AI did not cause outages but found so many issues that the rush to fix them before an attack overwhelmed systems washingtonsun.com/technology…

ophello avatar
⟳ ophello retweeted
ophello@ophello·Nov 17

Every single issue we've seen came on the heels of a "system update." There must have been some kind of trojan horse hiding in a bunch of JS scripts in a huge amount of open-source software that (once deployed) started causing problems in multiple connected systems.

ophello avatar
ophello@ophello·Nov 17

What in the ever loving hell is going on in the US? How many information networks have to be disrupted in a row before we get an answer? Microsoft. Air traffic control. Online banking. United Airlines. NSA. That’s five individual system outages, in the span of a week.

BREAKING: NSA Net, the US National Security Agency's highly classified network, has gone down and is experiencing an ongoing outage, per CNN. The network allows employees to communicate classified information internally. This follows several other major outages this week.

ophello avatar
ophello@ophello·Nov 17

You can ignore reality. You cannot ignore the consequences of ignoring reality.

Eli Greenfeld avatar
⟳ ophello retweeted
Eli Greenfeld@Eli_Greenfeld·Nov 16

Your money is fine, it's the login that's down. Good time to ignore any "urgent, verify your account" text that lands in the next hour, scammers love an outage...

Desire😎 avatar
⟳ ophello retweeted
Desire😎@desirewobo_·Nov 14

People need zero proof to believe a lie, yet endless proof to accept the truth.

ophello avatar
ophello@ophello·Nov 14

A terrific play-by-play of the ATC fiasco we just witnessed:

So let me get this straight. 2021: Biden's infrastructure law puts $5B into FAA air traffic control facilities. That means towers and buildings. It doesn't replace the decades-old copper-and-switches network that connects them. 2023: The FAA hires Verizon for $2.4B to build that replacement network. Two years later it still isn't running. Project 2025 calls for spinning air traffic control out of the FAA and privatizing it if possible. 2025: DOGE fires about 400 FAA staff, including maintenance mechanics at 18 air traffic control facilities that were already short on technicians. Musk pushes Starlink to replace Verizon. Newark's radar and radios keep going dark because of old copper wire and untested telecom links. Congress puts $12.5B toward the fix and calls it a down payment. June 2026: Air Space Intelligence wins a 12-year FAA contract worth up to $875.9M to build SMART, an AI air traffic management system. Months earlier, ASI's PAC donated to the campaign of Duffy's son-in-law. The award was competitive. ASI's Air Force deal was sole-source. November 10: SMART goes live at all 22 Air Route Traffic Control Centers, about 50 days after its first launch over Washington. The controllers' union says it wasn't involved in the rollout. November 13: An update hits the private network that links every center. The network reboots and crashes, the old equipment chokes, and controllers get bad data. The result is the third nationwide ground stop in US history: more than four hours, nearly 8,000 cancellations and 10,000+ delays. Officials blame old equipment. ASI and Duffy say SMART had nothing to do with it. DHS says it can't rule anything out. Nobody has said what the update was or who approved it. And an earlier review had already warned that this network was no longer supported and that one failure could cut off an entire region. Anyone who has shipped software into legacy infrastructure knows the appropriate playbook: ⭐️ Map every dependency. ⭐️ Test against real failure modes. ⭐️ Run old and new in parallel. ⭐️ Roll out in stages. ⭐️ Change one major thing at a time. ⭐️ Keep a rollback you've actually tested. ⭐️ Keep the operators in the room. I suspect a lot of newer engineers raised on vibecoding have never learned this. Prompting gets something new on screen fast, but it won't teach you how a decades-old network reacts to an update at 4pm on a Friday. Speed is not the metric. In aviation, reliability and accountability have to be built in from day one. Bring back the adults in the room.