Light Travels Faster Than Sound. That’s Why Some Folks Appear Bright Until They Speak. Amateur radio operator, Emergency Coordinator Ventura County ACS
@prayingmedic No way US did not know. Raids have to be coordinated to avoid friendly fire incidents.
I believe that Trump is playing from the Iranian proxy playbook:
“It was not us, the <insert proxy here> did it, we had no knowledge…”
@DISADOD Great spotlight on the Armed Forces Day Crossband Test, ham radio's reliability shines in contingencies!
But let's clarify: it's not just 'back to basics' or not a 'modern tech.' Our vibrant community pioneers cutting edge innovations like VARA FM (25k bps digital modes), Winlink global email via radio-only, AREDN mesh for VoIP/video, DSP, SDR, and beyond.
These make ham a dynamic partner for resilient comms asset that enhances interoperability especially in denied environments.
How can hams support DISA's next HF event and help you use ham radio cutting edge capabilities and technologies?
#HamRadio #DISA
Yarden Bibas is finally home—but his wife, Shiri, and their children, Kfir and Ariel, are not with him.
We stand with Yarden and the entire Bibas family.
🟧 Share this for Yarden, Shiri, Kfir, and Ariel.
So, here’s how my Tuesday went. Actually, let’s go back to Monday.
As many of you know, we share all credible threat reporting from our open-source al-Qaeda-focused Benghazi investigation directly with U.S. targets under threat—no exceptions. Yesterday, I shared information regarding a plot against a U.S. embassy that had evolved to the operational stage. Naturally, I shared this information with the embassy's RSO (Regional Security Officer)—the one person responsible for managing such threats—and the Ambassador, as they are the key target of any embassy threat.
Fast forward to today, and I receive an email from someone within the “Pentagon”—yes, they felt the need to name-drop it, as if that added weight to their words. Their complaint? That I didn’t share my information through the “proper channels.” I’d love for the community to explain the proper channels for sharing open-source information, as there aren’t any. In the last year alone, I’ve shared information from our investigation with six different organizations within the U.S. government.
But here’s the real issue: when it comes to threat reporting, there’s no room for bureaucratic games. The RSO is the proper channel when lives are on the line at an embassy. Yet, this is the broken system we’re dealing with—the “Pentagon” had a problem with it—a system more concerned with finger-pointing than taking action.
This isn’t the first time. Back in September 2022, I shared actionable intelligence containing the real-time location of Hamza bin Laden directly with the FBI, only to find myself under scrutiny instead of them focusing on the threat he poses. It’s beyond infuriating. Every minute wasted on emails like the one I received today is a minute not spent digging into a credible threat. What’s even more damning is that nowhere in their email was there a single question regarding the actual threat or a discussion of the safety of personnel at the embassy. Think about that.
What have we become? The mission used to be clear: protect those who serve. Now, it’s about some nobody gatekeeper standing in the way. It’s shameful.
Let me be unequivocal: I will continue to share threat information, especially with embassies, as I have lost multiple friends in attacks on U.S. diplomatic facilities. If that makes you uncomfortable, then maybe you should focus on collecting better intel and staying ahead of these threats. Frankly, in my opinion, we should be firing anyone who gets in the way of information sharing and protecting our people.
This isn’t just a critique—it’s a mission. Lives depend on us getting this right, and we must ensure that information is delivered where it matters most.