The tree involved with the Korean Axe Murder Incident
Talk is in the air that North and South Korea may finally sign a peace agreement that will officially end the Korean War. The guns mostly went silent with the 1953 signing of the Korean Armistice, but there were still outbursts of violence, such as the Korean Axe Murder Incident of 1976.
The Korean Axe Murder Incident began on August 18, 1976 when United Nations Command (UNC) forces (consisting of U.S. Army and Republic of Korea [ROK] troops) identified a poplar tree in the Korean Joint Security Area (JSA) of the DMZ that blocked the view in the summertime of a UNC checkpoint (CP No. 3) from a UNC observation post (OP No. 5). A work party of UNC soldiers, led by U.S. Army CPT Arthur Bonifas and USA 1LT Mark Barrett, was organized to trim the tree using axes and other tools.
This prompted a response from North Korean soldiers. A group of 15 North Korean soldiers led by a notoriously confrontational officer, Senior Lt. Pak Chul, tried to intervene, with Chul claiming the tree was planted by North Korean founder Kim Il Sung himself. The UNC troops promptly ignored Chul and his troops and returned to trimming when Chul ordered his men to kill them. In a skirmish lasting less than 30 seconds, Chul’s men killed Bonifas with one of the working party’s axes and then fled. Barrett managed to escape the initial attack and hid in a nearby depression but UNC forces did not notice he was missing until after North Korean troops had found him and also killed him with an axe.
To get a leg up in the investigation in the cold case of the “Golden State Killer” (aka the “East Area Rapist”), authorities recently turned to modern DNA and genealogy analysis tools.
But they didn’t use any of the big-name DNA analysis firms like 23andMe; instead they relied on GEDmatch, a free, open source site run by a small two-man Florida company that just a few years ago was soliciting donations via PayPal.
According to the East Bay Times, which first reported the connection to GEDmatch late Thursday evening, California investigators caught a huge break in the case when they matched DNA from some of the original crime scenes with genetic data that had already been uploaded to GEDmatch. This familial link eventually led authorities to Joseph James DeAngelo, the man who authorities have named the chief suspect in the case. To confirm the genetic match, Citrus Heights police physically surveilled him and captured DNA off of something that he had discarded.
Source: GEDmatch, a tiny DNA analysis firm, was key for Golden State Killer case | Ars Technica
I was reading this New York Magazine article about how the pioneers of the Internet were apologizing for what it has become, nevermind that many of the “pioneers” they mentioned were Johnny-come-latelys in comparison to the actual beginning of the Internet.
NYMag’s story did feature two actual pioneers, though computer pioneers more than Internet ones: Steve Wozniak and Steve Jobs. They included this photo and captioned it “Steve Jobs (left) in his parents’ garage in 1976, working on the first Apple computer with Steve Wozniak.”
There are a few problems with this photo and caption. First off, the photo is backwards. If you switch the photo to the proper orientation, you’ll be able to read that the text on the computer under Wozniak’s hand reads “Apple II.”
This brings us to the second issue with this photo and caption: it is not the first Apple computer (the “II” thing kinda gives this away). Apple’s first computer, the Apple I, did not come with a keyboard nor case. It was essentially a circuit board.
Was this photo really taken in the garage of Jobs’s parents? Wozniak has said that the whole garage thing is a myth and that no testing or production ever took place there. The photo shows a very neat-looking workspace with a workbench. According to what’s said to be the first news story on Apple Computer, the Steves were still working out of the Jobs garage when the article was written.
If there were GoPros when I was the Navy you’d get to see videos of me chipping paint, buffing passageway floors, putting down floor tile, and other exciting work! LT Evan Levesque, a Navy fighter pilot, used his to show us what it’s like to launch off an aircraft carrier’s catapult in an F/A-18 Super Hornet.
Looks like fun, doesn’t it?
TheDrive has the background on the pilot and his videos.
Love, sex, and political intrigue. A great read.
Lisa Howard had been waiting for more than two hours in a suite of the Hotel Riviera, enough time to bathe, dress and apply makeup, then take it all off to get ready for bed when she thought he wasn’t coming. But at 11:30 p.m. on that night in Havana—February 2, 1964—Howard, an American correspondent with ABC News, finally heard a knock at the door. She opened it and saw the man she had been waiting for: Fidel Castro, the 37-year-old leader of the Cuban revolution and one of America’s leading Cold War antagonists.
“You may be the prime minister, but I’m a very important journalist. How dare you keep me waiting,” Howard declared with mock anger. She then invited Castro, accompanied by his top aide, René Vallejo, into her room.Over the next few hours, they talked about everything from Marxist theory to the treatment of Cuba’s political prisoners. They reminisced about President John F. Kennedy, who had been assassinated just a few months earlier. Castro told Howard about his trip to Russia the previous spring, and the “personal attention” he had received from the “brilliant” Soviet Premier Nikita Khrushchev. Howard admonished Castro for the repressive regime he was creating in Cuba. “To make an honorable revolution … you must give up the notion of wanting to be prime minister for as long as you live.” “Lisa,” Castro asked, “you really think I run a police state?” “Yes,” she answered. “I do.”
Source: ‘My Dearest Fidel’: An ABC Journalist’s Secret Liaison With Fidel Castro – POLITICO Magazine
I’ve only seen carrier flight operations from the perspective of my destroyer sailing behind it, acting as plane guard. This is a good overview of what is actually happening there.
LCDR Joe “Smokin” Ruzicka, the last F-14 Radar Intercept Officer to fly the Tomcat Tactical demonstration, is back to walk us through exactly what it took to strap on a 70k pound F-14 Tomcat in the dark of night and successfully get flung off the front of a US Navy super carrier via one of the ship’s mighty steam-piston catapults.
I walk closely behind Corky through the passageway, making sure I have all of my gear strapped down while there is still a fraction of light. Once you step outside the hatch to the flight deck, it’s likely the only real light will be a partial moon hidden behind some clouds. Corky told me to grab the back of his survival vest once we stepped out onto the flight deck and not to let go. The flight deck of an aircraft carrier is simply too dangerous for a new guy to wander around on, especially at night and alone.
Immediately after you step outside, your senses strain to help your brain figure out what is going on. Your eyes see nothing. It’s too dark. You better have your flashlight out and pointed at the ground or you will step on something dangerous. Your ears hear the high whine of other airplanes turning just above you. The first thing you smell is jet fuel. Lots of it. The fumes are everywhere, but it’s not suffocating, just omni-present. Mostly, you just feel the rush of wind interspersed with an intermittent burst of jet exhaust. The wind might be hot or it might be cold, depending on the time of year and the location of the ship, but the exhaust is always hot. In any case, the air is definitely moving and it creates a noise inside your helmet that can be partially deafening.
Source: How To Successfully Get Launched Off A Carrier At Night In A F-14 Tomcat
Yet another security flaw with Intel chips.
Intel has addressed a vulnerability in the configuration of several CPU series that allow an attacker to alter the behavior of the chip’s SPI Flash memory —a mandatory component used during the boot-up process.
According to Lenovo, who recently deployed the Intel fixes, “the configuration of the system firmware device (SPI flash) could allow an attacker to block BIOS/UEFI updates, or to selectively erase or corrupt portions of the firmware.”
Source: Intel SPI Flash Flaw Lets Attackers Alter or Delete BIOS/UEFI Firmware