Titanic Chernobyl: the White House Unlearns National Security with Signal Starlink

We’ve witnessed what can only be described as how NOT to handle sensitive government technology and communications.

The installation of Starlink at the White House and the sloppy inclusion of a journalist in Signal chat for military strike planning represent a dangerous rejection of established safety protocols by those who apparently believe they are above the law and therefore untouchable.

Chernobyl Brain: Rules Are For Others

The Chernobyl disaster offers a powerful analogy for our current situation. What made that catastrophe so devastating wasn’t merely technical failure, but the Soviet organizational culture that enabled it: the casual bypassing of safety protocols, the dismissal of expert warnings, and the reckless improvisation during a sensitive procedure, all stemming from a Hegseth-like belief that catastrophic consequences simply wouldn’t apply to them.

When national security officials coordinate military strikes via a consumer device with a consumer OS and a consumer app on a consumer network, we’re witnessing a similar disregard for established protocols. The Germans recently learned this, as if anyone needs to be reminded the Russians are always listening to everything.

Just as Chernobyl operators manually overrode safety systems with a “we know better” attitude, today’s officials override digital safeguards by moving classified communications to platforms never designed for such use.

The most chilling parallel? The apparent belief that they are exempt from consequences. As Jeffrey Goldberg’s shocking report revealed, defense officials shared operational details, target information, and weapons packages WITHOUT OPSEC, likely and knowingly violating the Espionage Act in the process. When confronted about this breach, the official response demonstrated true Chernobyl Brain: “The thread is a demonstration of the deep and thoughtful policy coordination between senior officials. The ongoing success of the Houthi operation demonstrates that there were no threats to troops or national security.”

Uh, what?

This response echoes the initial Chernobyl reaction: nothing to see here during symptoms of meltdown; the system is still functioning; no real harm done. It reflects a worldview where security breaches are inconsequential as long as nothing immediately explodes, a very dangerous miscalculation of accumulating risk.

Titanic Legs: Unsinkable Hubris

The Titanic’s tragedy stemmed largely from a belief in its own invulnerability. Its operators ignored iceberg warnings and maintained speed in dangerous conditions, confident in their “unsinkable” vessel. The casualties were considered an acceptable risk – until they weren’t.

This same hubris manifests in the White House’s technology decisions. The casual implementation of Starlink, described by experts as “shadow IT, creating a network to bypass existing controls” shows misplaced confidence that borders on deadly arrogance. Even more telling is the bizarre implementation: Starlink dishes installed miles away from the White House, with the connection routed back through existing (tapped) fiber lines.

Why take this approach? Because they can create exposure and weakness for the Russians to exploit. Because consequences are flaunted. Because the rules that govern everyone, including federal records laws, classified communication protocols, and basic security principles, are treated as inconvenient obstacles to be challenged and ignored rather than essential safeguards.

When pressed about the inadequate Starlink safety a White House source dismissively explained that “the old was trash” as if an outrage of personal convenience justifies creating national security vulnerabilities. This mirrors the Titanic’s rejection of caution in favor of speed… right to the bottom of the ocean.

Consequences For Thee, Not For Me

What makes these security breaches particularly troubling is the clear double standards at play. The administration that campaigned on “lock her up” regarding weak communication protocols now coordinates military strikes via weak communication protocols. The same officials who emphasize borders for safety, routinely remove all the borders in technology.

This goes beyond carelessness because backed by the belief that consequences are for others. When the White House spokesperson defends the Starlink implementation by saying, “Just like the [insert any random name] did on numerous occasions, the White House is working to improve WiFi connectivity on the complex,” the message is clear: words have no meaning anymore because rules are no longer for those in power.

Improve?

The installation of parallel wireless systems creates security blind spots, monitoring gaps, and potential backdoors into sensitive networks. The use of commercial messaging apps on weak infrastructure for classified communications exposes operational details to potential interception. And most notable of all we have absolute proof the White House accepts lip service from Hegseth, when he’s obviously in breach of laws. Yet the attitude persists: we are untouchable; the damage to Americans won’t affect us when we move like Snowden to an apartment in Moscow.

From Recklessness to Disaster

Both Chernobyl and the Titanic demonstrate how quickly perceived invulnerability transforms into catastrophe. In both cases, the disaster wasn’t a bolt from the blue – it was the logical conclusion of accumulated shortcuts, ignored warnings, and systemic arrogance.

When officials treat national security infrastructure like a pig pen where established rules don’t apply to their mud slinging, they aren’t simply being careless, they’re setting the stage for predictable disaster. The accidental inclusion of a journalist in military planning didn’t lead to immediate catastrophe, thanks to the professionalism of that journalist, but it revealed a system where such accidents are not only possible but probable.

As one security expert noted regarding the Starlink implementation: “This is extra stupid to go satellite to fiber to actual site.” This isn’t the language of political disagreement, it’s the exasperation of true professionals watching rank muddy amateurs dismantle critical safeguards because they believe themselves immune to consequences.

Inevitable Reckoning

History teaches us that no one is truly untouchable, no matter how much they believe otherwise. The Titanic’s “unsinkable” reputation didn’t prevent it from sinking. Chernobyl’s operators’ confidence didn’t prevent catastrophic fallout.

The current approach to national security technology in bypassing established systems, ignoring expert warnings, and treating classified information casually, isn’t sustainable for another minute. These aren’t merely political choices; they’re fundamental security vulnerabilities that accumulate and worsen with time. Ask me about quantum threats in Signal.

When the inevitable breach occurs, when classified information is compromised (if not already), when military operations are exposed, when critical systems are penetrated, the consequences won’t be limited to those who created the vulnerabilities. Like Chernobyl’s radiation or the Titanic’s icy waters, the damage will spread far beyond those responsible.

Until the American people understand that no one is truly untouchable when it comes to security fundamentals, we remain on a collision course with consequences that no amount of privilege or power can deflect.

His OPSEC is a Lie: Hegseth Must Resign Now

Hegseth’s statement about being “clean on OPSEC” while simultaneously sharing sensitive military plans in an unsecured commercial app with an unvetted group that included a journalist shows a profound disconnect from reality.

1215ET: F-18s LAUNCH (1st strike package)
1345: ‘Trigger Based’ F-18 1st Strike Window Starts (Target Terrorist is @ his Known Location so SHOULD BE ON TIME – also, Strike Drones Launch (MQ-9s)
1410: More F-18s LAUNCH (2nd strike package)
1415: Strike Drones on Target (THIS IS WHEN THE FIRST BOMBS WILL DEFINITELY DROP, pending earlier ‘Trigger Based’ targets)
1536 F-18 2nd Strike Starts – also, first sea-based Tomahawks launched.
MORE TO FOLLOW (per timeline)
We are currently clean on OPSEC
Godspeed to our Warriors.

What’s particularly troubling is the contradiction between:

  1. Claiming to value operational security
  2. While completely failing to implement even basic security measures

The fact that detailed military strike plans were shared so casually, and that no one noticed an unauthorized participant for days, suggests either a complete lack of understanding about security protocols or a dangerous indifference to them, or both.

This kind of detachment from factual reality can be extremely dangerous in military contexts where lives depend on proper security procedures. History offers clear reminders of the consequences of OPSEC failures.

In 1961, the Bay of Pigs invasion collapsed partly because operational security was compromised—Cuban intelligence had detected preparations for the invasion, allowing Castro to mobilize and position his forces before the exiles even landed. The operation that was supposed to appear covert had become an open secret, with details appearing in newspapers like The New York Times days before the invasion.

Source: NYT

The impatient and sloppy approach demonstrated by Hegseth is especially concerning coming from senior defense leadership who should understand these historical lessons about the importance of protecting sensitive operational information.

It raises serious questions about competence and whether there’s a culture of saying the right words about security while ignoring the actual implementation of security measures.

Tesla FSD Can Only Full Self Drive 0.07% of a Typical Trip

When does a 1,400x safety gap become criminal negligence?

Tesla’s Full Self-Driving (FSD) technology has been the subject of dangerously failed promises every year since 2022 (unless you count it as part of the Autopilot failed promises repeatedly since 2016, shamelessly rebranded with a FSD fork of 2022). According to TeslaDeaths.com over 50 people have died during Tesla’s eight years of false safety promises. For those who have been asleep at their keyboard:

Since 2016 Elon Musk has promoted Tesla like a messianic gift, where driverless technology would arrive next year. And every year, as he gets richer for promising fantasy and instead delivering tragedy, it fails to come.

The latest Electrek data shows FSD has struggled to get above 200 miles between critical disengagements, achieving 400 at best.

For comparison, using Tesla’s own benchmark from the NHTSA for true self-driving capability, 700,000 miles between interventions is an equivalent to human driver safety levels.

This isn’t just a small gap to bridge. We’re talking about an improvement of 1,400 times better is required before Tesla could even begin to be considered as close to or safe as a human. With that in mind, Elon Musk has very prominently stated that this year Tesla will eliminate all crashes.

This year? 2025? Definitely not happening. Source: Twitter

Imagine if a pharmaceutical company announced they had a revolutionary cancer cure “ready for market” and going onto people’s bloodstream already, yet tests showed it was only 0.07% as effective as existing treatments.

Imagine boarding a plane advertised as “full self flying” that actually has a 99.93% chance of requiring an emergency intervention by the pilot during flight.

For six consecutive years, Elon Musk has promised FSD would achieve full self-driving “by the end of this year.”

Each deadline has passed without delivery. Now, instead of admitting the technical challenges, Tesla appears to be pivoting to attempting a 1950s concept of driverless. Their limited geo-fenced service – essentially adopting the same approach as RCA and GM before Musk was even born – has until now been criticized by Musk as “too difficult to scale.”

A 1950s RCA concept for geofenced driverless cars was promised to be reality by 1972. Source: Twitter

This matters because consumers have paid thousands of dollars for FSD capabilities based on these promises. Many purchased vehicles with the expectation that their cars would soon drive themselves, potentially increasing in value as “robotaxis.”

When examining the data and pattern of promises versus reality, it becomes difficult to view such Frank Abignale-like claims as unmoored optimism or detatched goal-setting. A 1400x performance gap isn’t something for patching over the air – it represents a fundamental chasm between current capabilities and promised functionality.

The Tesla brand promised an endless summer but has only delivered a colder and colder winter – a frozen wasteland of discontent, deception, and death

Regulators must recognize that a 1,400x gap between promise and reality isn’t just misleading marketing—it’s a public safety crisis demanding immediate intervention. Oh, I forgot, Elon Musk is using DOGE to get rid of the regulators who have said this already for years.

Tesla Fires Were Growing Long Before They Blamed Politics

2023 seems like a long time ago. Remember how the media basically ignored all the Tesla dealer fires back then?

Florida had a big one just last year, as did Massachusetts. A giant $300K damage one in California was interesting, particularly because Tesla said they couldn’t figure out the causes. Korea reported one too. And now we have another dealer on fire…

It is incredible just how many fires were happening for a decade already, with over 100 Tesla deaths reported by local news. Just food for thought when hearing that the government in 2025 wants to crack down on causes of Tesla fires.

Historical data from 2013-2023 | Projections for 2024-2026
Linear projection reaches ~65 incidents by 2026 | Exponential projection reaches ~95 incidents by 2026. Source: tesla-fire.com