Apparently you missed the Three hours, portion of the statement on how long the trip currently takes :). Words mixed with numbers are always confusing :)

Probably not exactly what you were asking for, but my all time favorite was back when I worked for an ISP, and we had a core router go down in the middle of the night. I get out to the POP and find that in order to get into the console of the router, I need to be able to plug a female 9 pin connector to a female 9 pin connector for the cables that I actually have with me.... I promptly found a couple of paperclips lying around and used my side cutters to cut off several lengths to short between the two connectors and make a gender-changer and Null Modem adapter in one, since it turned out I needed the null modem adapter too...

I see nothing in here about how they plan to address shared web hosting. To me that's always been more of an issue than the cost of the certificate.... Current implementations of SSL requires one certificate to be bound per IP address, and there is no "hostname" request from the browser like there is with HTTP. When I can pick up a certificate for less than $20 per year, the cost of the certificate is not going to hold me back... The fact that I can't install the certificate on my "Shared hosting" website, would however.

And in other news.. Water is still wet... Duh! i think by now we're all pretty aware the NSA was and is spying on pretty much everyone.

it's actually fairly common for any fairly new generation firewall that does Deep Packet Inspection for Intrusion Prevention, Content Filtering, etc. The firewall has to be able to view the data unencrypted to scan it for the "normal" stuff. Nothing overtly hostile in the intent there, just the way it works.

It goes beyond that though... AT&T already charges a higher prices for the "unlimited data" plans for their smart phones than almost any other carrier in the US... Plus they shouldn't brand it as an unlimited plan if they don't mean unlimited.

I actually got called out to a client this afternoon specifically to deal with this issue. It actually is more difficult than you think to recognize. From what I saw on his PC it actually wasn't picking up any of the files. It was registry keys. Unless you are specifically aware of the fact that Symantec Corporate Edition uses the Intel LanDesk registry keys you wouldn't have recognized it. Additionally once you ran it once, it automatically removed a few of the registry keys without even prompting. My client had stopped at the screen where it was showing that it had detected it and was asking what to do with it. Symantec was already broken. The registry keys that were removed were involved with the licensing. I had to perform the manual uninstall-Reinstall proceedure in order to get Symnantec back up and working. Apparently this was only the Feb 10th, definitions. He only had the problem on one PC, it had Feb 10th definitions. He had another that had already updated to February 11th, and it didn't have this problem. Additionally after I had fixed the issue on the PC that was effected I forced the update to the Feb 11th defs, and reran the scan. It no longer detected the Registry keys as the virus.