Hegseth is an Offense to Defense

The ongoing Signal chat leaks of Hegseth aren’t just breaches of protocol, they’re inevitable. They are the result of placing someone fundamentally unsuited for high office, lacking basic competence, into a position where lives depend on sound judgment.

As I documented in my earlier post, Hegseth’s background reveals troubling patterns that directly connect to these security failures.

The man decorated himself with crusader tattoos after, and perhaps because, hate-based extremism concerns were raised. The man proudly claimed to leave the military because it “didn’t want him anymore”. The man now casually distributes sensitive operational details through commercial apps to family members and personal associates.

This isn’t coincidence, it’s about character.

When a defense secretary creates not one but two unauthorized channels to share Yemen strike information with individuals lacking proper clearance, including his “producer/podcaster” family members, we’re witnessing the security manifestation of a deeper problem. Military professionals understand that protocols exist for reasons written in blood. Circumventing them reveals either dangerous ignorance or deliberate rejection of institutional safeguards or both.

Most telling has been Hegseth’s contrite response to being caught red handed failing at his job. Rather than acknowledging a dangerous breach, he immediately attacks messengers as “disgruntled” and claims critics are attempting to “slash and burn people and ruin their reputations.” The Pentagon spokesperson follows suit, dismissing legitimate security concerns as politically motivated “hit pieces.” Imagine being so untouchable and privileged that nobody around you can speak the truth without being labeled emotional or biased.

This deflection strategy serves a clear purpose: transforming objective failures of conduct into subjective questions of loyalty. It’s the same approach evident throughout Hegseth’s history. When basic standards are enforced, claim persecution; when caught violating protocols, attack the messenger.

The defense community deserves leadership that understands the simple gravity of operational security. Service members risking their lives in combat zones shouldn’t have their missions compromised because their civilian leadership treats sensitive information like political social media content. The American people deserve defense officials who accept crystal clear accountability rather than wallowing in muddy deflection.

As the great General Creighton Abrams once said, “Soldiers are not in the Army. Soldiers are the Army.” Their safety demands leaders who respect the systems designed to protect them, not someone who views security protocols as a personal convenience with no accountability.

The conclusion is inescapable: Hegseth has demonstrated what has been said about him before, that he cannot be trusted with the responsibilities of a military office. No amount of him attacking critics will change the reality he carelessly compromised operational security and endangered American service members for no good reason. National security, let alone the troops he claims to support, by definition require that Hegseth must resign.

“Tesla Tinderboxes”: Hong Kong Police Say the Brand is a Disaster

Tesla crash and burn so frequently in Hong Kong that police call intersections with them tinderboxes.

The company’s vehicles have become such constant fixtures in collision reports that some traffic officers privately refer to certain intersections as “Tesla tinderboxes.”

Notably, other popular brands don’t crash as often as the deadly Tesla, and some not at all, as we know from looking at data.

Source: IIHS

CA Tesla Kills One in “Veered” Early Morning Crash Into Tree

The crash time is similar to other recent Tesla fatalities from driverless, but police aren’t saying anything yet about it.

Police in Walnut Creek are investigating a fatal collision that occurred early Saturday morning. Police responded to Ygnacio Valley Road between North Main Street and North California Boulevard at about 2:40 a.m., according to Lt. Holley Connors, the Walnut Creek Police Department’s public information officer. Connors said the collision involved a Tesla that was driving eastbound, but declined to release further details

NY Tesla FSD Stopped by Police for Driving 30mph in Middle of Interstate

Another day, another Tesla driver who follows Elon Musk’s very unique and specific directions since at least 2015 to fall asleep in their seat.

On Friday, April 18, 2025, at approximately 12:29 AM, Troop H – Hartford Emergency Dispatchers began receiving multiple “911” calls about a Tesla traveling significantly below highway speeds on I-91 south in Wethersfield. Additional “911” callers reported they were observing the operator to be slumped over and presumably asleep behind the wheel. Troopers located the vehicle and observed it operating at approximately 30 mph with its four-way hazard lights activated in the center lane. Troopers also observed the operator slumped over, and presumably asleep behind the wheel while the vehicle was driving.

This incident raises critical questions about Tesla’s approach to safety protocols. When driver incapacitation is detected, why behave in a known illegal manner (C.G.S. 14-220(a) – Too Slow Speed) in an active traffic lane rather than safely pulling to the shoulder? The vehicle created a dangerous situation by setting itself to operate as a 30mph hazard in the center lane of an Interstate.

Notably, the 2015 Google driverless incident in Mountain View was for driving too slow, so this is hardly a new problem.

The multiple 911 calls underscore a fundamental design flaw: Tesla’s AI recognized something was wrong (hence activating hazard lights and reducing speed) but lacked the decision-making capability to follow the law and remove itself from traffic flow. The illegal AI behavior represents a concerning “fail-dangerous” rather than “fail-safe” approach to autonomous driving.

For a company that frequently (fraudulently) touts AI capabilities, the inability to implement such basic safety logic—pull over when driver is unresponsive—represents a significant gap between dangerous propaganda and operational reality. The incident demonstrates how even partial automation by unethical companies can create new risks because their safety protocols are so weak.