Adonis Diaries

Archive for December 4th, 2017

Japanese blogger questions the latest assumed photo of Amelia Earhart suggesting Japanese capture in 1937

 Magda Origjanska

It’s been 80 years since Amelia Earhart made her attempt to fly around the globe.

The unsolved mystery of her disappearance has recently taken a surprising twist as potential new evidence hit the news. An intriguing photo had surfaced, leading a handful of experts to proclaim that the legendary aviator may have survived the 1937 crash landing only to be captured by the Japanese.

The recently discovered photograph, supposedly taken after she crashed-landed on a remote South Pacific island, was the main topic of a History Channel special.

A former U.S. Treasury agent and expert named Les Kinney reportedly discovered the photo while combing through government records from the Office of Naval Intelligence while investigating Earhart’s disappearance. He discovered the photo in a “formerly top secret” file in the National Archives.

The photo was marked as “declassified,” with the following caption:PL-Marshall Islands, Jaluit Atoll, Jaluit Island. Jaluit Harbor. ONI #14381. With the photo undated, some analysts assumed that it depicted Amelia Earhart and her navigator, Fred Noonan. The photo depicts two blurry images on a dock, believed to be Noonan and Earhart who is staring at a nearby ship with her back turned to the camera.

It was analyzed by experts and analysts who argued whether it showed Earhart and Noonan. In the background, they identified the ship Koshu Maru and thus argued that possibly the Koshu Maru rescued Earhart and Noonan in 1937.

When Earhart embarked on her flight, many of the islands in the South Pacific were controlled by the Japanese. War would not break out between the U.S. and Japanese for another four years, immediately following the bombing of Pearl Harbor.

According to Kinney, the only reason why he was able to find the photo was that it had been misfiled.

He further insists that any document that referred to Earhart as a Japanese prisoner would have been deleted from an official file long ago to hide the fact that the government had been familiar with Earhart’s captivity but didn’t do anything about it.

The undated photograph was examined and evaluated by two top forensic photo analysts. One of them, the digital forensic analyst Doug Carner, claimed: “I can say with more than 99.7 percent confidence that the photo is authentic and untouched.”

Neta Snook and Amelia Earhart in front of Earhart’s Kinner Airster, c. 1921.

The startling theory suggesting a government cover-up is in contrast to the commonly accepted belief that Amelia’s life ended when her plane crashed into the ocean.

The leader of the team of investigators, Shawn Henry, stated: “This absolutely changes history. I think we proved beyond a reasonable doubt that she survived her flight and was held prisoner by the Japanese on the island of Saipan, where she eventually died.”

Amelia Earhart Plaque at Valhalla Memorial Park, North Hollywood. CA: Earhart Tribute at Portal of the Folded Wings. CC BY-SA 3.0.

In response to this provocative version of Earhart’s fate, a Japanese military history blogger has cast significant doubt on the photo. He claims that the found records of the photo that supposedly depicted Amelia Earhart surviving the crash landing in 1937 were published two years prior the vanishing of the famous aviator.

Known as @baron_yamaneko on Twitter, the blogger claims to have found evidence that the photo now being publicized predated Earhart’s disappearance. According to the blogger’s explanation, “the photograph was first published in Palau under Japanese rule in 1935, in a photo book …

So the photograph was taken at least two years before Amelia Earhart had disappeared in 1937 and a person on the photo was not her.” The blogger says the photograph, taken by Jaluit Atoll, was published in the photo book Umi no seimeisen: Waga nannyou no sugata, in the National Library of Japan.

Its publication date is listed as 1935. The photo book was digitized and published online by Japan’s National Diet Library. Its publication date, 1935, is listed in traditional Japanese style as “Showa 10.”

Amelia Earhart, Los Angeles, 1928 X5665 – 1926 “CIT-9 Safety Plane.”

The blogger added that the ship identified in the photo is actually the Koshu, a ship seized by the Japanese in WW1. According to him, the Koshu Maru was launched in 1937.

Talking to an open source software?

Alan posted this MAY 5, 2014 (selected as one of the top posts)

How to talk to an open source software project as a large scale or otherwise interesting user

The very short version: if you contact an open source project anonymously, you may Not get the best help.

Feel free to also reach out privately and share that your post from gmail.com is actually (say) from a very interesting deployment. Now read on for the long version!

Some months ago, the fine people from CloudFlare blogged about their new DNS implementation, and in that post they noted:

“While PowerDNS got us a long way, it started to run into issues as we scaled and dealt with an increasing number of large denial of service attacks … To their credit, the PowerDNS community responded to the first two problems with some efforts at rate limiting and other abuse detection”.

For us, this represented a sadly familiar pattern. We had lost CloudFlare as a user, and we had not been able to work with them sufficiently well to address their needs.

How did it happen, and why does it matter?

For an open source project, it is important to have happy ‘lighthouse’ users.

For years, we’ve proudly served the geodirection needs of Wikipedia for example. We’ve done a lot of work to keep various big users happy with their PowerDNS deployment.

If people know or find out your product is being used by ‘name brand’, large scale, deployments, this helps tremendously with adoption and acceptability.

In fact, next to development resources, a great community and funding, having impressive deployments is one of the most important things for an open source project.

So when we lost CloudFlare, other users contacted us to ask what had gone wrong, and if PowerDNS was still suitable for their needs.

We quickly reached out to CloudFlare, and Matthew Prince and co-workers sent us an impressive post-mortem on what had happened. They also graciously gave us permission to share the story, which is much appreciated.

It turns out they actually had shared their issues with the PowerDNS community, and they had gotten some help from us.. but not enough (by our own estimation). Importantly, they had not declared themselves as being a large or impressive deployment.

Now, we try to help everybody of course. We strive to be the friendliest name server community out there, and I think we are succeeding. But we can’t devote infinite resources to everyone.

Major users, major customers, interesting deployments need and get more attention. (It should be noted that we are also spoilers for users politely asking for help and willing to run test versions of our software, by the way. Nearly infinite help awaits you in that case!)

But, back to the subject of this post, here’s the problem.

Large or interesting deployments generally contact open source projects anonymously, mostly from gmail accounts, often even using fake names. And this is to be understood – in most large places (enterprise, public companies, government), sending out email to a world readable mailing list from a work email account is a sure way to get unwanted attention within your organisation (and get laughed at for your ridiculous multipage disclaimer).

Legal departments are likely to get their panties in a bunch – did you just share proprietary information? Security departments might ask if it was wise to publicly post company implementation details. Even the communication & marketing people might get in on the act. So email from gmail.com is what we get.

But this effectively means you might have a 500 server PowerDNS deployment doing really interesting things, things we’d love to help you with.. but we don’t know.

Not only is this a matter of scale, we may also not realise the nature of your challenge. If we know what you are doing, our thinking about your problem may run among different lines.

Another reason why employees at big corporations are loath to contact open source projects is that they assume they won’t get help, and need to pay for support. And, while it is true that someone needs to pay the bills here, we realise that for many users, a support agreement is just not going to happen.

Corporate IT might not even know the whole company is relying on an open source project. Questions might be asked. For such organisations, we are fine with providing free help on the public mailing lists. But to give proper weight and context to your issue, it helps if we know who you are.

So what about PowerDNS and CloudFlare?

From our conversation, we now fully understand why they wrote their own server.

But if at the time we had known the scale of their challenge, we would have loved to have tried to meet their needs. We do very much appreciate their help in the ‘post mortem’ of our silent breakup.

As Matthew said “[PowerDNS] is a great piece of software that met our needs well for almost 4 years. Today our needs are extremely unique and it wouldn’t make a lot of sense for you to try and design for them.”

Concluding, on behalf of PowerDNS, and I expect a lot of open source projects: If you are a large or interesting deployment, please do post to the mailing lists.

We do understand you will not be doing so from your corporate email account. But please do feel free to in parallel contact the project privately (IRC channels are typically a great way), where you can share more details of who you are and what you are doing.

Both you and the open source project will probably end up better that way.


adonis49

adonis49

adonis49

Blog Stats

  • 1,427,014 hits

Enter your email address to subscribe to this blog and receive notifications of new posts by email.adonisbouh@gmail.com

Join 774 other followers

%d bloggers like this: