For some reason, he didn't head off to Newfoundland; he went at tropical latitudes. If he was trying to follow a line of latitude due west to Asia, he was going the VERY long way. If he hadn't bumped into something along the way, he'd have been deeply screwed.

The direct route from Portugal to Japan would have taken him northeast. He probably had suspicions that the northeast passage wouldn't work, but the further north he went, the better. He'd have been better off going to Newfoundland. He would have failed to find the northwest passage, but he couldn't know that, either.

The explanation that he thought it was smaller would account for that. If he was going based on his suspicion that there might be something that far south, he had little evidence to support it, and was really staking his life it. It certainly paid off in spades, but that could easily have been a lie he paid for with his life.

I saw a 'gator right at the edge of the VAB parking lot last month. In a drainage ditch, up to the fence, cars parked right on the other side.

With luck, they'll start incorporating our radio transceivers. I hear that SpaceX flies with several USRPs now, so that's not completely unrealistic. That might be as close as I can get. Anyone who can get me a base invitation, though, would be greatly appreciated and I'd be happy to do some entertaining speeches while there. I need a base invite for Vandenberg, too. I got in to the official viewing site for the first try of the last launch (and that scrubbed too), but this next one is on Pad 6.

I was in Florida to speak at Orlando Hamcation and went to see the DISCOVR launch at Kennedy Space Center. I paid $50 to be at LC-39 for the launch, an observation tower made from a disused gantry on the Nasa Causeway between the pads and the Vehicle Assembly Building. A crawler was parked next door! A hot sandwich buffet, chips, and sodas were served. It was cold and windy! I watched for a few hours and unfortunately the launch scrubbed due to high stratospheric winds.

The next day, Delaware North Corporation, which operates tourism at KSC, decided not to open LC-39 or the Saturn 5 center for the launch. This was the third launch attempt and I guess they decided most people had left. I was annoyed.

The closest beach was going to be closed in the evening, it's a sensitive ecological area. I ended up seeing the launch from Jetty Park. This turned out not to be such a great location, the tower wasn't visible at all and the first 10 seconds of the rocket in flight were obscured before we saw it over a hill.

What's a better viewing location?

See, I was right. Stubborn, stupid, and there's no point in arguing with you.

If I email you from my Google account, where do those bits go? Who can read it once it leaves Google's servers? I don't know, because aside from SSL in transport, it's not encrypted.

Maybe you should think for 30 seconds before posting.

I, for one, don't really use Google+, but it's not because of any particular problem other than, "No one else is using it," with just a smidge of "I don't know what I'm supposed to be using it for," thrown in.

It does seem to me like "Hangouts" should be its own thing, along with chat and VoIP. If anything, those things should should sooner be integrated into Gmail somehow. I'm not sure I want that, but it would make more sense, at least, since it's all, roughly speaking, private communications.

I also think that there should be a separate web application that is, "Where my phone automatically uploads my photos, where I can organize them and track them myself, but they're private." Personally, it just makes me a little uncomfortable for that to be bolted straight on to the "photo sharing social networking site," but maybe that's just me. I'm old. I feel ok if the social networking site can connect in and pull photos from the private site. Hell, even if I know it's all ultimately stored in the database, that's not what bothers me. It's just to have my private stuff be in the same interface as the publicly shared stuff, without a clear apparent distinction... it worries my poor little monkey brain.

Ultimately, between Facebook, Twitter, and Google+, I tend to use Facebook for sharing posts/photos/updates. Not because I like it or think it's good, and only somewhat because my friends seem to use it more. As much as anything, I think it's because it's the site that confuses me the least.

There's not much point in arguing with you because you've shown that you're both too stupid to understand the point and too stubborn to actually think for 30 seconds before pushing your own tired nonsensical point.

But here's the thing in a very basic, simple, easy to understand explanation: End-to-end encryption doesn't suddenly become useless because you've trusted a 3rd party with the encryption keys. When you trust a 3rd party, then the encryption remains as strong as that 3rd party is trustworthy.

This is especially important to know, since we're already trusting other 3rd parties as part of the security chain. If I don't trust GPG or anyone auditing their code, then I can't trust the security of things encrypted with GPG, regardless of who has the keys.

Regardless, encrypting individual messages rather than relying solely on SSL during transmission does add security against various kinds of attacks and breaches. I could give examples, but do you want them? Would examples help, or are you, as I suspect, simply being difficult because you're an asshole who can't admit to being wrong?

Not needed if you've ever heard of Donald Knuth's reward checks, something that I'd expect most Slashdot readers have.

To clarify, I think it's pretty obvious to anyone who isn't dumb, and isn't being intentionally obtuse, that Gmail does not provide the level of security I'm suggesting.

So I guess the question is, which are you? An idiot, or an asshole?

Who said those were the things that I wanted?

2006 is almost a decade ago...

Just use a variant of the Donald Knuth reward check method. The first patent that gets invalidated will incur a 1 cent cut from the patent office budget. The second one a 2 cent cut, etc. After a few weeks the USPTA would have no option except shut down.

I'm not sure whether this is what you mean, but I think you may be missing the point with your talk about "real encryption". It is not necessary that no third parties can decrypt your data or messages in order to have encryption be useful. Security is not about absolutes. In almost all real-life security scenarios, there are requirements that you allow certain vulnerabilities, and that you trust some people.

For example, you can say, "With GPG, I don't have to trust anyone. I encrypt a message, and then the only person who can read it is the recipient."

But that's not strictly true. First, you're still trusting the recipient. That recipient could decrypt your message and make it public. Technology doesn't help you there. Additionally, you're trusting the recipient's security. If that recipient has malware that snoops on communications or grabs their private keys, the message can be decrypted. If that recipient has an untrustworthy spouse with access to the recipient's computers and passwords, then your information isn't completely safe.

Beyond that, you're trusting the makers of GPG. You're trusting that they know what they're doing-- that when they say their encryption can't be broken, they're right about that. You're also trusting that those people are not malicious themselves, and haven't left any backdoors available. You might argue that people can audit the code, but then you're just trusting the auditors. Even if you audit the code yourself, you're trusting your own understanding, which relies on the accuracy of your education on the topic.

So I'm getting kind of picky here, but the point is, if you understand security, then you understand that there is no situation without trust and vulnerability. The trick is to understand your vulnerabilities, and to be careful in choosing who to trust.

So if, in order to protect yourself from the data loss that would result in losing your keys, you choose to trust some other third party, that is not necessarily bad security. The trick would be in making sure you understood the vulnerabilities it exposed, and to choose the right people to trust. I'd rather trust Google to secure my email then I would trust the internet in general not to read my unsecured email.