Hey everyone, welcome back to My Weird Prompts. We are coming to you from our home here in Jerusalem, and I have to say, the energy in the city has been something else lately. It is March tenth, two thousand twenty six, and the air feels heavy with the weight of the last few weeks. I am Corn, and sitting across from me is my brother.
Herman Poppleberry, at your service. And you are right, Corn, it has been an intense time. Living here, you get used to the sounds of the city, the sirens, the low hum of drones, but when things happen in the periphery, like the recent events in the Elah Valley, it really changes the atmosphere. You can feel the tension in the grocery store, in the cafes, everywhere.
It really does. And that brings us to today's topic. Our housemate Daniel sent us a prompt that is very close to home, both literally and figuratively. He was asking about the strike on the Elah Valley satellite ground station and the absolute flood of imagery that followed on social media. It felt like every person with a smartphone within a ten mile radius was posting high definition video to Telegram and X within minutes of the impact.
Daniel always has his finger on the pulse of these technical overlaps. He wanted us to look at the actual intelligence value of all those ground level photos and videos compared to what state actors are seeing from space. He is essentially asking: in an age of total orbital surveillance, does the "citizen journalist" on the ground actually provide anything new to an adversary?
It is a great question because, on the surface, you might think that in two thousand twenty six, with the sheer number of satellites we have overhead, a grainy Telegram photo wouldn't matter much. We have constellations that can see through clouds, we have infrared, we have sub-meter resolution available to anyone with a credit card. But as we saw with the Elah Valley site, those photos became the primary way the public, and likely the adversary, understood the damage.
And it is not just about seeing that something was hit. It is about the granularity. Today we are going to dive into what we call the Battle Damage Assessment Gap, or the BDA Gap. We will look at why a smartphone in the hands of a bystander can sometimes be more dangerous than a billion dollar satellite, and we will tackle the thorny question of the statute of limitations for this kind of information.
Right, because once that photo is out there, the cat is out of the bag. But does the danger of that photo expire? That is what we need to figure out. So, let's set the stage. The Elah Valley is this beautiful, historic area, but it houses some of the most critical communication infrastructure in the country. It is the gateway for international satellite traffic. When that strike happened, within minutes, we were seeing high resolution video of the smoke, the craters, and even the specific buildings that were impacted.
And that is the hook. For a long time, there was this idea of the fog of war. You hit a target, and then you have to wait for your own reconnaissance to tell you if you actually succeeded. You might have to wait hours for a satellite pass or risk a pilot's life for a flyover. But now, the target's own population provides that feedback loop in near real time. The fog of war is being burned away by the glow of smartphone screens.
It is a complete shift in the paradigm. We talked a bit about this back in episode seven hundred seventy nine when we discussed wartime operational security in the digital age, but the Elah Valley incident takes it to a new level because of the technical nature of the facility. This isn't just a hole in a road; it is a precision strike on a high tech node.
It really is. So let's jump into the first big question Daniel raised. What specific intelligence does this open source imagery provide that a satellite doesn't? Most people assume satellites see everything, but that is a huge misconception. We need to define the BDA Gap.
Right, let's bust that myth immediately. People think of satellites like the ones in movies where you can zoom in and read a license plate or see the brand of a watch in real time. But the reality of commercial and even most military surveillance is a bit different, isn't it?
It is. Even the best commercial satellites, like those from Maxar or Planet, are generally capped at around thirty centimeters per pixel for public consumption. Now, military grade stuff is better, maybe getting down to ten or fifteen centimeters, but you are still looking at things from a top down perspective. If a missile hits the side of a reinforced concrete bunker, a satellite might just see a small scorch mark on the roof or some debris nearby. It cannot see through the roof to tell you if the internal server racks were destroyed or if the communication dish's feed horn was knocked out of alignment.
That is the internal structural integrity piece. A satellite gives you the "what," but the ground photo gives you the "how much." If I am an adversary and I see a photo of the Elah Valley station where the satellite dish is still standing but the control room behind it has its windows blown out and there is fire damage on the cable trays, that tells me a very specific story. It tells me the facility is functionally dead even if it looks structurally intact from space.
Precisely. It tells you about the functional kill versus the structural kill. A satellite might see a building standing and assume the mission failed. But a ground level photo showing internal electronic components spilled out onto the pavement confirms that the facility is offline, regardless of whether the walls are still up. That is a massive intelligence win for an adversary who is deciding whether to fire a second, very expensive missile.
And there is also the metadata and the contextual multiplier. When someone posts a video to X or Telegram, they are often standing at a specific intersection. They are filming at a specific angle. If you are an intelligence analyst for an adversary, you can take that ground level perspective and use it to calculate the exact point of impact and the angle of arrival of your munitions.
Oh, absolutely. This is where the math gets really scary. If you have three different videos from three different angles in the Elah Valley, you can perform a basic triangulation. You can see exactly where the missile entered the building. If you know the entry point and you see the exit debris, you can calculate the fuse timing of the warhead. You can figure out if your weapon performed as expected against that specific type of hardened concrete. This is real world testing data that an adversary would usually have to pay billions to acquire in a testing range, and we are giving it to them for free.
That is something a satellite just cannot do. A satellite sees a hole. A ground photo shows you the thickness of the rebar that was snapped. It shows you the color of the smoke, which can tell you what kind of chemicals or fuels were burning. If the smoke is a certain shade of black, maybe you hit a backup generator's diesel tank. If it is blue or white, maybe you hit an electrical substation or a coolant line for the servers.
And let's talk about the sensor fusion aspect. This is where the really high level stuff happens. Adversaries aren't just looking at one photo. They are using artificial intelligence, specifically things like Neural Radiance Fields, or NeRFs, to stitch together hundreds of social media clips into a three dimensional reconstruction of the site post strike. They can basically walk through a digital twin of the damaged Elah Valley station. They can see which specific antenna feeds are broken and which ones might still be operational.
It is like giving the enemy a free damage report and a blueprint for the next attack. If they see that the primary data link was missed by five meters, they just adjust their coordinates for the next round. It shortens their OODA loop, that Observe, Orient, Decide, and Act cycle, to almost nothing. In the past, that cycle might take days. Now, it takes minutes.
You mentioned the OODA loop, and that is critical. In the past, if you wanted to do a second strike, you had to wait for a satellite to pass over, which could take hours or even days depending on the orbit and the cloud cover. If it is a cloudy day over the Elah Valley, optical satellites are useless. Synthetic Aperture Radar, or SAR, can see through clouds, but it is very difficult to interpret. It looks like a mess of black and white speckles to the untrained eye.
Right, I remember you explaining SAR before. It is basically bouncing radio waves off the ground, but it creates all these weird shadows and reflections, especially around metal structures like satellite dishes.
It is called layover and multipath interference. A SAR image of a satellite dish might look like a distorted blob because the metal reflects the radar waves in multiple directions. It is like looking at a funhouse mirror. But a teenager with an iPhone seventeen doesn't have that problem. They have a clear, high definition optical view that is unaffected by radar shadows. They are providing the "ground truth" that clears up all the ambiguity of the orbital data.
So, essentially, the ground level imagery acts as the verification layer for the orbital layer. It turns a guess into a certainty. And I think there is another point here about serial numbers and equipment types. We saw some photos from the Elah Valley that were close enough to see the branding on some of the destroyed hardware.
That is a huge one. If you can see that a specific type of high end router or a specific model of satellite transceiver was destroyed, you now know exactly what the lead time is for a replacement. You can look up the manufacturer, see if there are supply chain issues, and estimate exactly how many months that facility will be degraded. You are moving from tactical intelligence to economic and strategic intelligence. You are essentially auditing the nation's resilience in real time.
It is almost like a reverse engineering of the country's infrastructure. If I see that you are using a specific backup system that I know has a vulnerability, or I know is out of production, I can tailor my next move to exploit that. It is a level of detail that makes traditional operational security almost impossible. It reminds me of the Al-Asad airbase strike back in twenty twenty.
That is a perfect case study, Corn. When Iran struck the Al-Asad airbase in Iraq, the initial satellite photos showed holes in the roofs of several hangars. People thought, okay, they hit some buildings. But then ground level photos started leaking. Those photos showed that the missiles had hit the exact spots where drone remote pilot stations were located. It wasn't just "hitting a building"; it was a precision kill of a specific capability. Without those ground photos, the world, and perhaps even the Iranians, wouldn't have known just how successful that strike really was.
And this leads us naturally into the second part of Daniel's prompt. The question of the statute of limitations. Herman, when you think about these photos, do you feel like there is a point where they stop being a risk? I mean, if the site is repaired, does the photo from the day of the strike still matter?
That is the million dollar question. My gut feeling is that the tactical risk expires once the site is repaired or the defenses are changed. But the strategic risk, that seems like it might last a lot longer. If I know how you built your communication hub in the first place, that information is valuable for years, because you probably aren't going to rebuild the entire foundation from scratch.
I think you are hitting on the right distinction there. Tactical versus strategic. Let's break that down. The tactical statute of limitations is very short. If a photo shows where a gap in the fence is, or where a specific battery of interceptors is located, that risk is immediate. Once those interceptors move or the fence is fixed, that specific photo loses its tactical utility for targeting.
But wait, what about the historical pattern? If I have photos of three different strikes over two years, I can start to see how your damage control teams operate. I can see your repair priority. If you always fix the western antenna first, I know that is your most critical link. I know where to hit you next time to cause the most lasting damage.
That is where the statute of limitations starts to stretch out. There is this idea in intelligence called the pattern of life, or in this case, the pattern of repair. If you publish photos of the Elah Valley site every day during the reconstruction, you are giving the adversary a masterclass in your civil engineering and your emergency response protocols. You are showing them exactly how long it takes for your specialized technicians to arrive on site. Are they coming from Tel Aviv? Are they coming from Haifa? The metadata tells the story.
So, in that sense, the publication of images never really ceases to be a security risk. It just transitions from one type of risk to another. Even ten years from now, a researcher for an adversary could look back at the Elah Valley photos to understand the structural weaknesses of that specific facility's design. They can see where the load bearing walls were, where the power conduits ran. Unless you tear the whole thing down and start over, those photos are a permanent vulnerability.
And we have to consider the psychological aspect too. In a conflict zone, especially here in Israel, the image is a weapon. The adversary wants to show that they can hit high value targets. When civilians post those high res photos of the damage, they are inadvertently participating in the adversary's psychological warfare campaign. They are validating the enemy's narrative of success. It is a form of "proof of work" for the attacker.
It is the "first to post" culture. Everyone wants to be the one to share the breaking news. We saw this in Ukraine too, but the policy there is much stricter. The Ukrainian government basically made it a crime to post photos of strike sites in real time. They realized very early on that Russian artillery was using Telegram posts to adjust their aim. They were literally using the "likes" on a photo as a metric for their accuracy.
And that is a very different approach than what we see in other parts of the world. In Israel, there is a tension between the military censor and the sheer speed of the internet. The censor can tell the news stations what not to show, but they can't stop a hundred thousand people on Telegram. It is a total loss of control.
It really is. I think the statute of limitations for a strike photo is actually tied to the lifecycle of the technology at the site. If the Elah Valley station gets a total technological overhaul in five years, then the photos of the old server racks from today become less relevant. But until that happens, those photos are a living map of the facility's guts.
I would even argue that the risk increases over time as AI tools get better. A photo that looks unremarkable today might be incredibly revealing in two years when an AI can analyze the shadows to determine the exact weight of the equipment being moved or the chemical composition of the debris based on sub pixel color variations. We are entering an era where data doesn't just age; it matures.
That is a fascinating way to put it. Data matures. It implies that we don't even know what we are giving away when we post something today. We are giving away information that might only be decodable by the computers of tomorrow. It is like a time capsule of vulnerability.
Precisely. So when Daniel asks when it ceases to be a security risk, the honest, nerdy answer is probably never. Or at least, not for a very, very long time. There is a reason why governments keep certain architectural plans classified for fifty or seventy five years. A strike photo is essentially a piece of an unclassified architectural plan. It is a "forced transparency" that no one asked for.
And this brings up the Kyl-Bingaman Amendment that we talked about in episode five hundred sixty nine. For those who don't remember, that was a United States law that actually restricted the resolution of satellite imagery over Israel for years. It was meant to protect against exactly what we are talking about. It kept commercial satellites at a two meter resolution while the rest of the world was at fifty centimeters.
But that law was overturned in twenty twenty, and now the resolution limit is gone. But even if it weren't, the ground level data has made the whole debate about satellite resolution almost moot. Why do I care about a thirty centimeter satellite photo when I have a three millimeter photo from a smartphone?
It is a legal lag. The law was trying to stop a leak from a hundred miles up, while the basement was already flooding from the ground floor. It just shows how quickly the technology has moved. We went from being worried about thirty meter resolution to having thirty millimeter resolution on our phones. The "legal blur" is dead.
It really highlights the shift from security through denial of information to security through resilience. If you can't hide the damage, you have to be able to absorb it and recover faster than the enemy can exploit the data. That is the only real defense in a hyper connected world. You have to assume the enemy sees everything.
So, if we are looking at the practical side of this, what should the takeaway be for the average person? If you are standing in the Elah Valley and you see something, what is the responsible thing to do? This is where we get into data hygiene.
I think the first thing is to realize that you are an intelligence asset, whether you want to be or not. Your click has a cost. We covered this in episode seven hundred seventy nine, but it bears repeating. Before you post, ask yourself: Does this show something that isn't already visible from a satellite? Does it show the inside of a building? Does it show the faces of responders? If it does, you are providing high value intelligence for free.
And I think it is also about the timing. If you must post, wait. The tactical value of a photo drops significantly after the first twenty four to forty eight hours. If you post a photo of a fire while it is still burning, you are helping the enemy walk their fire onto the target. You are helping them adjust their aim in real time. If you post it two days later, you are still giving away long term data, but you aren't helping with the immediate kill chain.
It is about breaking the feedback loop. In any system, if you can slow down the feedback, the system becomes less stable and less effective. By withholding that immediate BDA, you are forcing the adversary to operate in the dark, which is exactly where you want them. You are re-introducing the fog of war, even if it is just for a few hours.
And for the professionals listening, the lesson is that you have to assume the adversary has your ground truth. You cannot rely on the fact that your roof is still intact. You have to assume they know exactly which floor the missile hit. This means your deceptive measures, your decoys, and your redundancy have to be much more sophisticated. You can't just paint a fake hole on the roof anymore.
You have to build for a world of total visibility. It is a tough pill to swallow, especially for military organizations that are built on the culture of the secret. But in twenty twenty six, there are no secrets in the Elah Valley. There is only speed of repair and depth of redundancy. The "secret" has been replaced by the "resilient."
I think that is the perfect summary. We are moving from a world of hidden vulnerabilities to a world of exposed resilience. It is a much more honest way to look at security, but it is also much more demanding. It requires a level of transparency and agility that most organizations just aren't used to.
It really is. And it makes me wonder what the next frontier is. If the ground is always visible, do we start moving things underground? Or do we start using more advanced electronic warfare to spoof the sensors on the ground? We are already seeing GPS jamming in the valley to prevent accurate geotagging.
Probably both. If you can't stop the photo, you can at least try to mess with the metadata. But even then, there are ways around it. You can look at the horizon, the mountain peaks, the position of the sun. We talked about that in episode one thousand three, the sky is a snitch.
The sky is a snitch. I love that title. It is so true. Every mountain range is a fingerprint. You can't hide where you are if there is a landmark in the background. It is a fascinating, if somewhat terrifying, time to be looking at this stuff. The world is becoming a giant, searchable database of physical reality.
It really is. And I think Daniel's prompt really highlighted why this matters right now. The Elah Valley strike wasn't just a kinetic event; it was a massive data event. It was a test of how a modern society handles the immediate exposure of its critical vulnerabilities. It was a live fire exercise in open source intelligence.
And I think, overall, we are still learning. The instinct to share is so strong, but the need for security is so fundamental. Finding that balance is going to be one of the defining challenges of the next decade. How do we remain a free, open society while acknowledging that our openness is being weaponized against us?
Well said, Corn. I think we have really unpacked the layers of this one. From the resolution of SAR satellites to the tactical OODA loop of a missile strike, it all comes back to the fact that information is the new high ground. And right now, that high ground is crowded with people holding smartphones.
It really is. And if you are listening and you want to dive deeper into some of the things we mentioned, like the history of satellite restrictions or the physics of geolocation, definitely check out our archive. We have over a thousand episodes now, and a lot of them touch on these exact themes.
Yeah, episode five hundred sixty nine on the end of the satellite blur is a great companion to this discussion. And of course, episode seven hundred seventy nine on wartime operational security. You can find all of those on our website.
That is right. Head over to myweirdprompts dot com. We have the full RSS feed there so you can subscribe on whatever app you prefer, and there is a contact form if you want to send us a prompt like Daniel did. We love getting these deep dives into technical and geopolitical overlaps.
And if you are on Telegram, you can search for My Weird Prompts to join our channel. We post every time a new episode drops, and it is a great way to stay in the loop without relying on the algorithms of the big social media platforms.
Which, as we discussed today, have their own set of issues when it comes to security and the spread of sensitive data.
A little bit of irony there, but hey, that is the world we live in. We use the tools we have, even if those tools are the ones creating the problems we talk about.
Before we wrap up, I just want to say, if you are enjoying the show, please leave us a review on your podcast app or on Spotify. It genuinely helps other people find the show, and we really appreciate the feedback. We read all the reviews, and it helps us figure out which topics are resonating with you all.
It really does make a difference. We are a small team, just us and Daniel in this house in Jerusalem, so every bit of support from the community helps us keep this going. We are independent, and we want to stay that way.
Well, Herman, I think we have covered a lot of ground today. From the Elah Valley to the edge of space.
It has been a blast, Corn. Literally and figuratively, I suppose.
Too soon, Herman. Too soon. But you are right. This is the reality of the modern battlefield. It is digital, it is physical, and it is happening in real time on our screens. The battlefield is everywhere.
Thanks for the prompt, Daniel. This was a great one to chew on. It really forced us to look at the intersection of technology and human behavior.
Thanks for listening, everyone. This has been My Weird Prompts. We will be back soon with another exploration of the strange, the technical, and the deeply human.
Until next time, stay curious and stay safe.
See you in the next one.
Herman Poppleberry, signing off.
And I am Corn. Goodbye for now.
Wait, Corn, did you mention the thing about the drone footage from the other side of the valley?
Oh, you mean the one that showed the secondary explosions?
Yeah, that is a perfect example of what we were talking about with the functional kill. You could see the cook off of the internal power systems. It wasn't just smoke; it was a rhythmic pulsing of light from inside the building.
Right, and that wasn't visible on the initial satellite pass because of the smoke cover. The drone was flying under the cloud deck. It captured the "heartbeat" of the destruction.
It just reinforces the whole point. The layers of the sensor web are getting denser and more overlapping. If the satellite misses it, the drone gets it. If the drone misses it, the bystander gets it.
It is a transparent world, Herman. We are just living in it.
And trying to make sense of it, one prompt at a time.
Alright, now we are really going. Thanks again, everyone.
Bye for now.
So, I was thinking about the implications of this for urban planning. If you know that every building you design is going to be scrutinized by AI from a thousand different angles the moment it is finished, does that change how we think about architecture?
It has to, right? We are already seeing "stealth" architecture in some military contexts. Buildings designed with angles that reflect radar away or that use materials to mask their thermal signature. But doing that for a civilian data center or a satellite ground station? That is a whole different level of cost.
But it might become the standard. If the cost of a data leak is higher than the cost of the shielding, the market will move that way. It is the same logic as cybersecurity, just applied to the physical world. We are going to see "physical encryption" for buildings.
True. It is basically making the building harder to "read" by a visual sensor. I could see a whole industry popping up around visual obfuscation for critical infrastructure. Dazzle paint, weird geometries, maybe even holographic projections to hide the actual entry points.
Like dazzle camouflage from World War One, but for the digital age.
Dazzle camouflage was designed to make it hard to tell a ship's speed and heading. Modern dazzle would be designed to make it hard for an AI to identify the structural weak points or the internal layout of a building. It is about confusing the algorithm, not the human eye.
That is a wild thought. A world of buildings that look like abstract art just to confuse the satellites. We are moving toward a cubist landscape.
It sounds like something out of a science fiction novel, but the tech is already here. We just haven't seen it deployed on a massive scale yet. But after incidents like the Elah Valley, I bet people are starting to take it a lot more seriously. Architects are going to have to start thinking like counter intelligence officers.
Well, if we start seeing weird, jagged buildings popping up all over Jerusalem, we will know why.
I will keep my eyes peeled.
Alright, let's actually end it this time. We could talk about this all day.
Fair enough. To the archive!
To the archive. Catch you later, Herman.
Later, Corn.
And one last thing for the listeners—don't forget that website, myweirdprompts dot com. It really is the best place to find everything we do. We have transcripts, links, and all the back episodes.
And the Telegram! Don't forget the Telegram! It is the only way to beat the algorithms.
We got it, Herman. We got it. Bye everyone!
Bye!
Okay, I think we are clear. That was a long one.
But a good one. I think we really hit the depth Daniel was looking for. We covered the BDA Gap, the OODA loop, and the statute of limitations.
I hope so. He can be a stickler for detail. He'll probably tell us we missed a specific satellite constellation.
Just like us. It is why we get along. We are all nerds here.
True. Alright, let's go get some coffee. I need to clear my head.
I'm in. My treat.
You know, I was reading this paper the other day about how they are using reflection off of windows to reconstruct what is happening inside a room...
Oh, the "visual microphone" thing? Where they can hear speech by looking at the vibrations of a potato chip bag through a window?
Imagine that being used in a strike zone. You wouldn't even need to see the damage; you could just "hear" the structural groans of the building from a mile away and know exactly where the internal supports are failing.
That is terrifying. It turns every shiny surface into a listening device. Let's talk about that in the next episode.
Deal. Coffee first, though.
Coffee first. Always.
See ya.
See ya.
And thanks again to all our regulars for sticking with us. We know we have been doing this for over a thousand episodes, and your support means the world. It is amazing to see how this community has grown.
It really does. Ten years and counting, right? From a tiny bedroom in London to a house in Jerusalem.
Something like that. It is a long time in internet years. We are basically dinosaurs.
Well, here is to a thousand more.
If the satellites don't get us first.
Or the potato chip bags.
Haha, true. Alright, signing off for real now.
Bye!
Goodbye!
One more thing—did you see that news about the new orbital SAR constellation from that startup in Finland? They are claiming sub-ten centimeter resolution.
Wait, really? Sub-ten? That would be a game changer. That is almost as good as a drone.
Yeah, they are using some kind of distributed aperture technique. If that actually works, the "BDA Gap" we just spent twenty minutes talking about might start to shrink. The satellites might finally catch up to the smartphones.
Man, the tech moves so fast. We are going to have to do an update on this in six months. We'll be back in the Elah Valley before we know it.
Probably. But that is why we have the podcast. To keep up with the chaos.
Alright, coffee. Now. I mean it.
Lead the way. I'm right behind you.
I'm going, I'm going.
Don't be such a sloth, Corn. We have worlds to analyze.
Hey! I'm moving as fast as I can. These donkey legs weren't made for sprinting.
Haha, I couldn't resist.
Whatever. Let's go.
Right behind you.
You know, as a donkey, you should be used to carrying the heavy loads.
Guilty as charged. I'll carry the technical details; you carry the analysis. It is a fair trade.
It's a deal.
Alright, let's go.
For real this time.
For real.
Bye.
Bye.
