Tag Archives: bomb

Fukushima Contamination Hype: Facts, or “Fear Porn”?

Fukushima Contamination Hype: Facts, or “Fear Porn”?

 

The following image represents tsunami wave heights — NOT radiation levels.
http://defensetech.org/2011/03/12/noaa-map-of-japanese-tsunami-wave-height/

Fukushima-Contamination-Pacific-Ocean-450x253

Introduction

Fear about Fukushima and its “poisoning of the Pacific” is rampant these days. On Facebook, some of my “truther” friends get angry if I dare to question the reality of a nuclear apocalypse looming in and over the Pacific.

The term “fear porn” has gained a lot of traction, and in this instance I can see why: intelligent people have become so addicted to their Pacific Ocean horror fixation, they refuse to evaluate any data that might contradict it.

Are there dying animal populations? Should residents of the Pacific Northwest be concerned? Does the Pacific Ocean contain large amounts of radioactive material? While the answer to all these questions is “Yes”, there is, as usual, a lot more to know.

Mainstream media outlets peddle the lie that all four obliterated reactor containments at Fukushima remain unbreached. Meanwhile, the so-called “alternative media” has been hammering truth seekers with dire claims that are equally misleading.

These two false scenarios – one, everything is under control, and two, the Pacific Ocean has been destroyed – constitute the usual goalposts by which people are routinely deceived, manipulated, and distracted from reality.

Usually, the goalpost dialectic leads the public down a predetermined path of brainwashed opinion, and reality is somewhere outside the confines of the posts. In this case, however, reality is not only outside the goalposts, but in between them as well.

Let’s look at the latter reality first.

Animal Die-Offs

Yes, there was a starfish apocalypse. Dead starfish by the millions littered the ocean floor off the British Columbian coast. Their arms were falling off. Their guts were gooshing out. When marine biologists collected them in tanks for analysis, they sometimes turned to jelly before they reached the laboratory.

“Alternative news” sites such as ENEnews.com promptly attributed the die-off to radiation from Fukushima. Droves of truthers, already terrified by reports of radioactive tuna and Google Maps images showing the killer radiation overtaking the Pacific like a psychedelic oil slick, fell for this bit of disinformation hook, line, and sinker.

The truth is that die-offs are a regular occurrence in nature. Die-offs happen when populations outstrip food supply; malnourishment leads to starvation and, more importantly, disease, which quickly propagates, effecting a population crash.

After the crash, the survivors, presumably the fittest, enjoy less competition for a recovering food supply, and the population rebounds.

Dr. Craig McClain, Assistant Director of Science for the National Evolutionary Synthesis Center, identifies the syndrome that caused the die-off, and gives three reasons why it had nothing to do with Fukushima: (1) as an observed phenomenon, it predates Fukushima by 3 – 15 years; (2) it also occurs on the East Coast; and (3), other forms of life in the region remained unaffected.

Far from being unusual events, animal die-offs happen all the time, and normally go unremarked by all but the scientists who monitor them. Unscrupulous outlets ENEnews.com and Rense.com, among many others, are now hauling reports of them into the alternative media limelight and attributing them to Fukushima fallout without presenting a shred of evidence.

In doing so, they spread not only disinformation, but needless fear.

FukuKrakon

Atmospheric Fallout

There have been claims of high Geiger counter readings in the Pacific Northwest.

According to Jim Stone, the engineer and ex-NSA analyst who proved that Fukushima was an act of environmental terrorism, the nuke that destroyed Reactor 3 did indeed produce particles that were blown eastward and are most likely to end up in North American riverbeds.

That isn’t good, but neither is it the end of the world, when one considers the many Cold War nuclear test detonations, one factor in the cancer rate explosion of the 20th century.

This article from Geigercounter.com traces high readings in California to naturally radioactive sand. How many amateurs with Geiger counters are erroneously jumping to Fukushima conclusions?

Background radiation is not uniform. Naturally occurring hot spots vary widely in intensity. In some parts of Iran, people thrive in radioactive norms much higher than any in the United States.

It makes sense to take the Geiger counter reports with several grains of salt.

Stone makes another good point. In Washington State, police cars are equipped with Geiger counters, which still sometimes detect radiotherapy patients. The background radiation in that region has not spiked because of Fukushima; otherwise, the cops’ Geiger counters would be jammed and useless for detecting cancer patients.

Some particles from the obliterated core of Reactor 3 have found their way to North America, but the reality does not begin to approach the hype.

“The Pacific Ocean is DYING!”

This is where people have been getting most emotional, and understandably so. We love whales and dolphins, and a whole lot of us enjoy seafood too. How much more catastrophic can you get, short of a planetary mass extinction event?

But this claim, that “The Pacific Ocean is dying”, is the most tenuous of them all.

The Pacific took its worst hit when Reactor 3 exploded, sending a portion of its fuel downwind over the waters. The rest will sit on Japanese land, making much of it uninhabitable, for as long as Japan remains above sea level.

Water happens to be an ideal radiation sink. Even gamma rays cannot penetrate more than two and a half feet of seawater. It takes only a fuel pool with a little water to soak up all the radiation from many reactor cores. Meanwhile, the Pacific Ocean occupies fully 30% of Earth’s surface.

Consider also the many nuclear tests conducted in the Pacific during the Cold War. In that context, are we to believe that a bit of fuel from one reactor core could destroy the entire ocean?

Even had Reactor 3’s entire core been ejected into the water, the idea that it could poison the entire ocean is ludicrous.

Conclusion

If you are freaked out by the hype, I suggest that you consider the possibility that you are getting roped in by a fear porn campaign designed to … do what?

Now we come to the reality outside the goalposts.

Stone thinks that the disinformation is to divert truthers’ attention from the real issues surrounding Fukushima: that (1) the disaster on 3/11/11 was a coordinated attack on Japan, (2) the majority of environmental damage outside Japan came in the immediate wake of that attack, and (3) the most serious issue is all the expelled fuel still strewn around Reactor 3’s destroyed containment. So lethal is that debris that not even robots can survive proximity to it. Safe disposal remains untenable.

I think the “elites” enjoy scaring the masses. In a sense, they feed on it. Fear is an excellent tool for keeping people’s minds in chains, especially when they happen to be a demographic (frequenters of “alternative” media) who are consciously trying to shake off those chains and become mentally free.

Stone’s report proving that 3/11/11 was an act of war is available in PDF format here.

jimstonefreelance.com

farganne.wordpress.com

Advertisements

Kimberly Dvorak Spreads Ridiculous Claim About Hastings Engine

In more than one appearance on San Diego’s Channel 6 News, “investigative” journalist Kimberly Dvorak has stated that the engine from Michael Hastings’ Mercedes c250 landed behind the wreck — defying, in her own words, the laws of physics.

She even claims to have consulted university professors. Here she commences dispensing this rank nonsense at the 2:00 mark:


I am astonished that such statements can be received with straight faces. Yes, the crash did happen in Hollywood, but only in cinematic productions are the laws of physics defied.

I will now show you where the engine really landed.

Here is a screenshot from the Loudlabs footage, taken at the scene after the crash:

engine_loc_llabs

Note the streetlight pole to the left. Note also the manhole cover and the concrete slab it sits in, as well as the trees leaning over the sidewalk.

All of these are clearly visible in the following aerial shot from Google Maps —  click to enlarge:

Highland-Clinton

That is the northeast corner of the intersection of North Highland Avenue and Clinton Street.

Zooming out — again, click to enlarge:

Highland-Clinton2

The car was speeding south on Highland as indicated by the white arrow.

The yellow flash indicates an explosion that took place. This explosion demolished the front end of the car and threw the engine southeast.

That is the only way the engine could have reached its final position.

Had the car hit the tree fully intact, the engine could not have passed through the tree, much less flown down the block.

I think two bombs were involved: one that destroyed the front end and threw the engine, and one that blew the gas tank, which could account for the massive fire. My analysis leading to this conclusion takes into account and matches up the damage to the car and to the tree:

https://farganne.wordpress.com/2013/06/28/two-car-bombs-at-the-hastings-crash-the-evidence/

Long story short, the Mercedes was already a wreck when it hit the palm tree, rotated, and landed, burning, in its final position facing slightly southeast.

There were many long days when outside of eating, sleeping, and answering to Nature, my sole activity was studying the details of that crash scene and deducing a scenario that explains all its oddities.

I’m glad I wasn’t trying to swallow food when I saw Kimberly Dvorak on TV telling the world that the engine landed north of the wreck, behind it.

I sent a “friend request” to Kimberly on Facebook. She accepted it. I did not complain publicly on her timeline. I figured she had just gotten it backward somehow and decided to give her the benefit of the doubt. So I sent her private messages politely pointing out her error, providing a link where she could see for herself where the engine really landed, and asking that she correct it.

In Facebook, when you send a private message to someone, and they click in the message window, you are notified that the message has been seen.

Kimberly Dvorak saw my messages, and she never did respond.

Next thing I knew, I was watching a video of her up on RT news, spouting the same utter nonsense about university professors declaring that the laws of physics had been violated by the engine landing behind (north of) the wreck.

I have not yet seen Kimberly Dvorak retracting these ridiculous statements.

If she really did consult “university professors”, and they corroborated her nonsense, then they did not take the time to become familiar with the crash scene.

If she truly believes that the engine landed behind the wreck, then she should not be trusted as a source of information, especially when she ignores reliable sources of it.

Two Car Bombs at the Hastings Crash — The Evidence

Two Car Bombs at the Hastings Crash — The Evidence

[NOTE: If you read this article a few days ago, please consider re-reading, as it has been substantially updated, and now includes a mathematical analysis of the engine/tranny throw. Also, there is one detail that absolutely proves the car did not hit the tree intact. This detail is found in the update at the end of the main body of the article below.]

First, in case you are unfamiliar with the crash scene, a brief orientation.

The car crashed into a palm tree on the median adjacent to 621 North Highland Avenue (west side). It was traveling due south. An aerial shot from Google Maps:

aerial_crash_bearings(Click to enlarge)

The red arrow represents the car’s trajectory until it swerved eastward onto the median. The indicated palm tree is the one it struck. The red ‘A’ thumbtack is 621 North Highland.

The car struck the tree on its north-by-northwest side — that is, if you were to face the tree looking due south, the initial impact zone on the trunk would be slightly off-center to the right. That is where the bark is cleanly chewed away. In the following photo provided by Jim Stone forum member Doug, you can see that the impact damage extends around the west side of the trunk, dissipating as it goes:

trunk_nw

Note that to the extreme right of the trunk (southwest side) you can see the end of impact damage and after that there is only charred bark. This damage pattern indicates that the car struck the tree and rotated counterclockwise if seen from above. It ended up facing just south of due east. Yet there are no skid marks on the grass or asphalt from the back tires, indicating that they were airborne during the rotation.

Here is another shot provided by Doug showing scorched grass and asphalt but no skid marks on either. Doug took it from the west side of the avenue, in front of 621 N. Highland, facing east. The swath of scorched grass tells us the car’s orientation as it burned.

impactedtree_doug

So, it is established that the car struck the tree slightly to the west on its north side and rotated with rear wheels airborne to the position indicated by the scorched grass area.

How and why did that happen? I’ll call this The Rotation Question, and I will answer it below.

First, we need to look at the engine, which was thrown 130 feet to the southeast and landed near the northeast corner of Highland Ave. and Clinton Street. First, a view from the ground, grabbed from the Livelabs footage appended at the end of this article:

[Note: Some guys have jumped on me — “That not the engine, that the transmission, your a moron!” — okay, I’m not a car guy. Whatever. That thing is heavy and it flew a long way.]

engine_loc_llabs

You can see the streetlight (left of engine), the concrete area with manhole it sits on, and the two leaning trees (right of engine) both in the following aerial shot and from Maps street view:

engine_loc_maps(Click to enlarge)

The car hit the tree on its north-by-northwest side. The engine ended up 130 feet southeast of the tree. Even assuming that no bombs were involved, the obvious question is, how did the engine clear the tree? It could never have flown through it!

I’ll call this the Magic Engine Question. Again, I’ll answer it below.

[Update: After reading this report, my engineer friend Bruce got curious and did some calculations on the engine flight, proving that even if the tree weren’t in the way, the car would have had to be going 250 mph to throw the engine that far — and that doesn’t even factor in the bolts fastening the engine to the car. His presentation is here: Simple Physics Calculation]

Next, I direct your attention to the debris field extending from the wreck area in a southeasterly spray pattern toward the blown-out engine.

On the east side of the avenue, facing southwest, engine down the road, off-screen, to the left:

debrisfield_sw

Facing northwest, toward the wreck:

debrisfield_nw

The debris field is extensive and far-reaching. I cannot consider it consistent with a mere high-speed impact.

Had it just been a high-speed impact, the front end ought to have been “wrapped around” the trunk of the tree, as you’ll see below.

But all that debris came from somewhere, and here it is — a mostly missing front end:

frontendgone2

The sheet of metal to the left of the tree is the Mercedes’ hood, wrapped around its south side. Here’s a due-south grab from the median:

frontendgone3

Now think about this for a minute. Take a good, hard look, and THINK.

Is there some quality about palm trees that makes them incredibly destructive to the front end of an impacting vehicle?

For quick reference, here are some shots of high-speed front-end impacts. Click on them for the sources.

truck_tree
cartree2

car_crash_tree

The person who posted this next one claims the driver was an uncle going 200 kilometers per hour, or 125 mph:
large_crash

Click on this next one and you’ll see an assortment of similar photos, non of the wrecks burned, and none with detached hoods:

OLYMPUS DIGITAL CAMERA

Based on this evidence alone, I am convinced  there was a bomb in the engine compartment that destroyed the Mercedes’ front end and threw the engine. Since the cab was not destroyed, it was a directional bomb designed and placed to project the force of the explosion toward the front of the car.

Whiz kid Jim Stone forum member Glitch had this to say on the subject:

@Farganne Excluding the impossibility of the engine clearing the tree, the engine would not have gone 130 feet away from a collision alone. First, the engine would have to break free of its mounts, which are by no means weak. Then it would have to rip through the hood&frame in order to exit the engine compartment. After all of that, it would have to still have enough force from the momentum to travel 130 feet. Now, the engine in a Mercedes-Benz is not big, and weighs around 800-1200 lbs, and after ripping through the frame, it would not go very far. I don’t include math in this one as there are so many factors that are difficult to mathematically quantify, (the force to bust through the frame) and I don’t want to sit here all day doing it.

Moving on, here is a view of the wreck from the east side of Highland, facing due west:

crash_eastside

Note that the top of the cab is caved in. Again, there’s the hood, twisted around the left (south) side of the tree.

The right front wheel looks to have been blown forward and cocked at an angle almost perpendicular to the rest of the car. It didn’t appear that way before the 2:00 mark of the Loudlabs footage, but it did afterward. There were secondary explosions during the time the car sat burning, so this bit of damage may have resulted from one of those.

Either that, or the wheel we see in this shot is actually the left front wheel blown over and obscuring the right front wheel from this angle.

Next, we need to take a look at the fire.

hastingsfire

Many have been quick to point out that a Mercedes is not a Pinto. It doesn’t just burst into flames on impact with a tree. The gas tank in this vehicle is situated at its rear anyway. I think Jim Stone was correct in his assessment of the fire. It was instantly all-engulfing and incredibly intense. Such a fire could only have been initiated by a gas tank bomb, and I am taking that as a given.

I will close the focus on the fire by noting that Jose, the Spanish-speaking witness in the Loudlabs footage, though struggling to express himself in English, clearly indicated (3:45 – 3:48) that the car was on fire before it hit the tree. That tells me the gas tank bomb went off before the car hit the tree.

Now, after spending probably dozens of hours squinting at this scene from all angles, and visualizing scenerios to find one that explains all the observations I have made thus far, I am going to tell you what I think happened.

As it passed the two closely-spaced palm trees to the north of the impact palm, the car swerved left onto the median.

At that moment, both the gas tank bomb and an engine compartment bomb simultaneously went off.

Now for some Newtonian physics — equal and opposite reactions. The gas tank bomb caused the rear end of the car to lift. At the same time, the kick-back from the bomb in the engine compartment provided a counteracting “downward-and-backward” force.

The car flew toward the tree at reduced speed with its rear end raised and nose lowered.

Going in slow motion now. The blast threw the hood into the tree. It threw the engine down the street. At this point, there would still have been sufficient distance between car and tree for the bomb to throw the engine past the tree and down the street. This would be the point of origin of the debris field.

The hood hit the tree and wrapped around it.

At that point, before the hood fell, the car hit the tree with two impact points: first, whatever forward-projecting metallic scraps remained of the lower chassis (base of the trunk), followed by the upper edge of the windshield (higher up the tree).

The wrapped-around hood shielded the tree from surface abrasion at the upper impact point.

The Mercedes hit the tree slightly to the left of its own center. Forward momentum made it rotate counterclockwise (viewed from above) while falling to its final position, rear wheels airborne the whole time.

As it rotated, the wrapped hood went with it and ended up curved around the tree’s south side.

It fell in a heap where you see the scorched grass.

Loudlabs arrived, and I have had a headache ever since.

I believe that the car was remotely controlled.

And that is how I see it having happened.

Here is the Loudlabs footage:

Update:

Jim Stone forum member tigerwolfe made this valuable observation:

I believe I have identified a piece of the debris field from the limplobs video at around the 4:50 mark. While viewing the vid, I’d seen this peice many times, Like I’m certain many others have too. Could not ID it, so I ignored it.

It turns out to be from the nose of the Mercedes. The part of the front bumper to which the front license plate attaches. The front California license plate is NOT in the bracket, and could NOT get out without removing the white plastic trim.

This piece found on the road is NOT a piece from a car that hit a tree head-on at 100mph. And this piece did NOT come from a car that was currently licensed in CA.

A frame taken from the video:

And close-ups with a 2013 Diamond Silver Metallic Mercedes-Benz C 250 Coupe superimposed.

I will add this to tigerwolfe’s observation:

Q.E.D.

_____________

Addendum 1:

Was there a driver in the car?

I offer for your inspection these two shots. Is that a crash dummy head?

head_side

head_front

_____________

Addendum 2:

There has been some confusion about this shot. At first glance, it doesn’t seem to match the crash scene, but actually it does.

telescopic

The denser, more crowded appearance of palm trees is due to telephoto lens distortion. The sign with the arrow above the car is way down at the intersection with Clinton Street. The telephoto lens magnified it.

From this shot it is also obvious that they shifted the wreck and removed the driver’s door after they extinguished the fire. Why, I don’t know.

___________

Addendum 3:

In my humble opinion, anyone claiming the Mercedes was hit by a Hellfire missile is either deliberately or mistakenly full of it. For reasons that should be obvious by way of the preceding analysis.

Over and out.

Proof That A Car Bomb Killed Michael Hastings?

Disclaimer: When I first posted this, I was excited and maybe too sure of myself. I am not an expert in these matters. So I offer the following evidence to support my current thesis that a car bomb in the engine compartment destroyed the front end of the Mercedes and lobbed the engine down the street. I have been alerted to at least one precedent for engine ejection upon impact, so I wonder what a bomb could do.
________________

Note: Jim Stone has stated that the following image is from a photo op scene with a switched car at a switched location. I don’t know. Even if that is true, the footage showing the obliteration of the car’s front end was taken at the scene, when it was still dark.

When I first saw this tableau, I immediately wondered: WHY THE BLANKET?

0:59

Now I know. It’s because the front end of the car is almost completely GONE.

Check out these still shots, taken from Loudlabs News footage (posted below):

blownapart

The carriage and rear end are cocked back from a blast that cleared the engine compartment. The right front wheel and part of the front bumper are about all that’s left, and they are cocked forward.

Now from the driver’s side angle:

frontendgone2

Note what looks to be the hood twisted around the left side of the palm tree.

Now, a direct side shot:

frontendgone3

The blanket was there to hide the fact that almost the entire front end of the car is gone.

Only a bomb could have done that.

Perhaps this explains the flight of the engine down the street. I leave that to the more technically-minded to decide.

Jim Stone’s analysis: http://www.jimstonefreelance.com/hastingsmurdered.html

Update:

A member at the Jim Stone Forum argues that such damage is consistent with a normal high-speed tree impact. That may very well be. But Stone’s analysis has already shown that this was no ordinary car fire.

That raging fire, in my opinion, would not happen from a bomb-free impact. Car experts agree.

Consider, too, the eyewitness testimony at 1:11 of the Loudlabs footage below, where she states that the car “exploded upon impact” with the tree.

Also the other eyewitness who told the local news reporter that her house shook and her windows rattled — that it sounded, and felt, like a bomb had exploded.

Then there’s the engine down the street.

Finally, I went to Google Images and looked up some high-speed vehicle-tree collisions. They are indeed incredibly destructive.

But look at that last photo again:

frontendgone3

Seems to me that there is a lot of “gap” between the tree and the cab of the car, and no wreckage in there — just empty space.

Had the car hit the tree at high speed, causing all that damage, I think the cab would be scrunched right up against the trunk. Like when they say that Jed “wrapped his Camaro around” a telephone pole.

It looks to me like the car bumped into the tree and that triggered a detonation.

Here is the Loudlabs footage:

____________

Appendix:

Note: Unless you are a Jim Stone Forum reader, this will not be significant to you.

blownoutsctn blownoutsection

Questions about the Death of Michael Hastings

According to the following article from the Los Angeles Times, Buzzfeed and Rolling Stone announced Hastings’ death on Tuesday:

http://www.latimes.com/local/lanow/la-me-ln-coroner-no-identification-michael-hastings-20130618,0,5825533.story

Yet, as the very URL of that article makes clear, the coroner had yet to identify the body. Absent a positive identification, how were Buzzfeed and Rolling Stone confident enough to make that official announcement?

The rest of this article will focus on a single newscast, which yields enough incoherent information to indicate that Hastings’ death was not the result of an accident. All subsequent still shots are taken from it, except for those from Google Maps.


First, according to all accounts, the car was a brand-new Mercedes.

No car will blow up from getting run into a tree, least of all a Mercedes. And yet:

rochellefran51

An eyewitness claims the blast was so intense that it shook her house and rattled her windows.

Those L.A. palm trees must be made of something more than wood. Hell, everything in Hollywood is fake anyway. Maybe those palm trees are made of some kind of plastic. Like C4.

Moving on, our next eyewitness is Hollywood producer Gary Grossman, whom we can thank for America’s Funniest Home Videos (1989):

grossman107 garygrossman109 engine113

He says the engine flew 50 or 60 yards and landed near a telephone pole. Other accounts say 100 feet. Who’s counting? How does any car, much less a Mercedes, hit a palm tree and explode with enough force to throw the engine ANYWHERE???

Vin Diesel would blush at a script like that. Not even a hack like Gary Grossman could conceive of writing it. What does that tell you?

For the record, here is Grossman’s address from the Hollywood White Pages:

grossmanaddress

546 North Highland Avenue. I decided to plop myself down there on Google Maps. Here is the scene of the “accident”, from left to right.

highland1 highland2 highland3

Do you see how SPACIOUS it is? LOOK at all that SPACE! And yet they say Hastings, in the darkness at 4:30 a.m., smashed his Mercedes into one of those toothpick palm trees with enough force to cause an explosion that sent the engine flying some distance, any distance at all. Impossible. Even in Hollyweird.

Even if a collision took place, was he blind drunk? If so, what are the odds he’d hit one of those trees? If he wasn’t blind drunk, then he was suicidal. Why would a suicidal man pick a palm tree in the middle of a residential neighborhood?

After Grossman’s testimony, we get this chilling eulogy from the talking head:

hastingsencomium130

Hastings will, likely, partially be remembered? That is very deliberately worded. Whoever had the bomb put in Hastings’ car hated him with the passion of a billion white-hot suns, and wanted to crap all over his accomplishments by delivering that insult unto his legacy.

And who has the power to make sure that the slight is worded just so, via the mainstream news?

I’ll give you a hint: the answer rhymes with “news”.

Still stumped? Oh well, take a look at who was first on the scene, except for Grossman:

jewishgroup

Here’s the first responders’ website:

http://www.hatzolahofla.org/

Make sure to turn your speakers down before you click, or they will offend your eardrums as well as every other atom of your being.

Jim Stone’s take is here: http://www.jimstonefreelance.com/hastingsmurdered.html

For more on how cars do not turn into bombs upon impact with trees:

http://www.thetruthaboutcars.com/2013/06/famed-non-automotive-journalist-michael-hastings-turns-a-c250-into-a-bomb/

_____________

Tinfoil Hat Addendum:

They waited until Hastings was 33.

Reactor 4 = Fukushima’s Building 7

fkshmrctr4

Building 7 at the World Trade Center was not hit by a plane. Yet it collapsed at freefall speed on 9/11/01.

Reactor 4 at Fukushima was offline, defuelled, and disassembled on 3/11/11.

It exploded anyway.

That’s about as possible as cooking a TV dinner in an unplugged microwave oven …

… absent a bomb.

Israel Nuked Syria — PROOF

NO TE: If you try to share the following link via email, or mention Stone’s name in the body of your email, it is likely to get “lost”. The best way to spread this info is to download and share this .gif

http://www.jimstonefreelance.com/rogue2.html

Nuclear rogue

Permalink
Those of you who are new to this site probably do not realize exactly how censored your news is. I suggest you read the following to find out. Yes, they absolutely WILL try to hide a nuclear blast, provided Israel did it and the target was Arabs.

The real issue at hand now is that Israel has proven itself out in the open, under documented irrefutable conditions, that it considers nuclear aggression acceptable policy. This means that for as long as Israel exists it is a menace to the world. It is fairly well proven that Israel caused the Indonesian tsunami, nuked Bali, caused the Japan tsunami, nuked Fukushima, and FINALLY, because an Arab set a decent camera up at exactly the right place and time, and had the balls to post the video immediately, it is proven and not a guess that Israel is a nuclear rogue.

I did not get the best screen grab for what I showed in my initial analysis, and when I was doing further work on this report, I landed on the holy grail – the moment of criticality. I did not know the camera captured this.

israelnukingsyria

Here you can see that even in the part of the frame that was not the sky, even in the shadow areas, there was so much light that the camera sensor clipped to it´s maximum value at all sensor sites. You can extract this frame from the cleanest version of the original video, Here is the most pristine version of the original video ever posted by the man who shot it. I made sure this got preserved. A powerful computer or advanced video editor will help. You won´t be grabbing this frame with an old Celeron.

I cannot begin to emphasize enough how impossible it is to clip a camera sensor to maximum, even in the shadow areas. This means that even the windows in the buildings took in so much light that the normally dark area inside the buildings which would make the windows appear dark got so much light that even the super dark areas clipped the sensor. The sun will not do that, even with a massive over exposure. The only thing that will do that is a nuke, which is well known to be brighter than the sun.

This is the proverbial “no damage from a 9.0 earthquake, other than tsunami damage” proof that is needed to show this was a nuke. Anyone should be able to understand this, and you don´t need to know photoshop, you don´t need to know focal lengths and lens behavior, just look at the frame grabs below. They say it all and you do not need to be an expert to see it.

frame1

The following captures give you a clear reference for what is happening in the frames above. Put your finger on one of the flames in the frame above to see where it is in the picture while the light of the nuke is still overwhelming the camera so badly it cannot see that flame. How bright is the sun? Would that camera be able to see a fire at high noon? Obviously yes, and this proves that even after significantly fading, the nuke is STILL brighter than the sun.

There is only ONE THING WE KNOW OF, THAT CAN LIGHT THINGS BRIGHTER THAN THE SUN. THIS ALONE IS PROOF ISRAEL NUKED SYRIA

nukefade

We now know what a nuclear attack looks like for real, and it is surprisingly Hollywood. We also know now that EMP is B.S., and that an ordinary camera can survive filming it. As I have always said, nuclear EMP is a HOAX that is going to be used as an excuse to get rid of technology via Intel CoreVpro processors, other 3g enabled processors, and via the 3g connections ALL AUTOMOTIVE CONTROL COMPUTERS AFTER 2004 HAVE ON ALL THE TIME, as well as smart meters which can probably command appliances to auto destruct, which will be used to fake the public into believing a nuclear EMP wiped everything out when in fact it was only the zionists using decades old 3g technology to tell everything to self destruct with a system we all forgot about. And THAT is how they will throw us back to the stone age, and accomplish our final enslavement.

This video is proof positive that our electronics are NOT susceptible to nuclear EMP, a fact I have been harping for a long time now, and all it took for me to know was to put pen to paper and calculate it out.

EMP fear mongering is a mind game, to get people to waste their efforts on that which is irrelevant. EMP from a nuke is a threat to ONE thing – a device hooked up to a wire over a mile long that has no protection circuit. Nuclear EMP needs a conductor with a cross section a mile long to couple with, it´s all very easy math. Your car, your laptop, your cell phone is immune, simply because it is too small to take in the signal. Power distribution systems, phone systems, ethernet computer networks with no fiber optics, and cable TV systems can be damaged but even then it is not likely, the nuclear tests of the 40´s 50´s and 60´s took place amidst power lines and phone networks, and the ONE time anything did get blown out it was a rotary multiplexer at a small local phone provider. Our modern stuff is far more robust simply because over time it was improved to survive lightning strikes.

But nuclear EMP is not the issue here, IS IT?

I´d say NO. The real issue at hand now is that Israel has proven itself out in the open, in documented irrefutable conditions, that it considers nuclear aggression an acceptable policy. This means that for as long as Israel exists, it is a menace to the world. It is fairly well proven that Israel caused the Indonesian tsunami, nuked Bali, caused the Japan tsunami, nuked Fukushima, and now, simply because an Arab set a decent camera up and had the balls to post the video immediately, it is PROVEN BEYOND ALL DOUBT AND NOT A GUESSING GAME THAT ISRAEL IS A NUCLEAR ROGUE. I gotta laugh – it was their “eternally illiterate mud hut goat herder” patsy that nailed them. Hey Israel, WHO ARE WE SUPPOSED TO BE TRUSTING WITH A BOMB?? Looks like the movie Airplane and many others were nothing but kike fantasies. The damage you caused to the reputation of others while being even WORSE filth yourselves is the pinnacle of all hypocrisy.

Even more damning is the blackout in the media – all forms of it. I can excuse some of the alternative media that has limited staffing for missing this, but CNN, FOX, AlJazeera, ABC, NBC, CBS, ALL latino news outlets, EVERYTHING “mainstream” has staffing good enough to know what went on, and their silence is absolutely DAMNING. It proves beyond a shadow of a doubt that we are all wrapped up in a blanket of zionist lies, disinfo, and SILENCE.