Does this benefit the population at large or does this benefit corrupt officials and the large corporations that corrupted them?

And then there is unreliable which can allow for awesome statistics, for instance they could tell the FCC that Netflix is 105% faster than Hulu but that the way it works is that Netflix has a 5% packet loss that are perfectly selected to cause the most trouble with the data stream.

Also if these paid agreements are so "reasonable" why not buy exclusivity? That is that when these companies negotiate their fast lane contracts to make it exclusive fast lane access; that is to basically pay to block the competitors out. So Hulu could buy the all the fast lane access for video subscription streaming locking out Netflix. Or google could buy up all search engine access.

Plus this would then give comcast incentive to make an ever greater divide between the two speeds and keep slowing down the slow lane. I suspect that the ever shrinking legroom in economy is increasing first/business class ticket sales.

Basically allowing any form of non-network neutrality will only make a few scumbags richer and the rest of us greatly poorer in both money and quality of services.

A fair percentage of people who travel on airplanes are assholes; plain and simple. So to give another tool for these douchbags to continue their assholery is just stupid.

A great move for the airlines would be to de-shithead their passenger lists by banning the use of mobile on the plane. I would happily travel on any airline that had a no cellphone rule for the simple reason that any remaining airlines that let people use their phones would magnetically attract the wankers away from the awesome airlines.

I suspect that there will be magically connection rates but this will just be a dickwad amplifier in that the people who use the phones will be government and large organization types on an expense account and will be ultra fartbreaths while they are talking since the calls will cost so much.

But on a more serious note allowing cellphone use on airlines will be stupendously dangerous seeing that some vigilantes will take jammers with them. While cellphones have been pretty solidly proven not to interfere with the avionics I am fairly certain that a jammer would have a substantially negative effect.

To give an example of just how much of a crap-for-brains type of person I am expecting I will give a recent restaurant experience. There was a guy in a very small restaurant who kept getting calls on his phone that he was not answering on his very very loud phone that didn't have voice mail. So basically the phone was ringing for about 50 percent of the time that I was in the restaurant. The fattened pig of a human being just sat there ignoring the phone and the horrible effect that it was having on anyone else. The owners of the restaurant were there and did nothing (as I would expect most airlines to do). What would this guy do on an airplane at 2am? Let the phone ring for 4 hours straight, or silence it? BTW the guy was not deaf.

I do have a happy ending, when my lunch friend and I went to both drop our 1 star Yelp reviews we saw two others relating to the same incident. The four 1 star reviews made up over a third of the total reviews; smashing the 4 star rating to 2 stars. Cellholes can really piss people off.

Lightning can easily give off Xrays and even Gamma rays. So would it also be possible that these people who have this blast right along their skin are also getting a solid dose of radiation.

There are huge swaths of things that I don't understand about most technologies that I use. I could not even begin to enumerate the various obscure ways that "const" can be used in C++. But I have deployed many product using C++. The same with SQL databases which I have huge amounts of data happily going into and out of. These things work as well as I could hope and my understanding of them is well sufficient for me to be happy. I suspect that if I hired a top of the line C++ or SQL expert that both my code and my databases could be vastly improved from a working well to working even better.

But with both of the above examples, not only did the products get deployed but as new functionality was required no real barriers were hit during development. But with MongoDB basic data in/data out functionality was developed and deployed. But as new functionality was required the fight with MongoDB became a huge waste of time.

And my credibility comes from the fact that the same functionality was easily deployed in other tools learned before and subsequent to MongoDB. My point being that it was time wasted on a technology that absolutely did not live up to the hype. I didn't say that my MongoDB couldn't do it(who knows) but that the potholed road to getting there was not worth driving when a smooth traffic free 8 lane highway existed going in the same direction.

So my recommendation is to use MongoDB if you want to look cool in 2012 and like to flagellate yourself.

I tried MongoDB and I even tried to like it. I do love NoSQL but what I came to realize was that MongoDB was trying to tell me how to solve my problems instead of just storing my damned data.

But the real problem with MongoDB was that nearly everything, while appearing simple, required a google search to figure out how to do it. A mark of a very well designed API is that you soon start guessing the commands and your guesses are really close or right on. But with MongoDB I found that nothing really made sense. Only after carefully crafted "debate team" arguments could any unusual aspect of MongoDB defend itself. Whereas redis is the opposite, it just works. Or even simpler systems like Memcache, that couldn't be simpler, when read the API for either of those they just made sense. There is no layer upon layer upon layer of complexity. It is data goes in, and data comes out.

In fact redis would be a good example of ease of use mixed with advanced capabilities. The basic commands are things like get, append, save, while more advanced commands are more esoteric such as PEXPIREAT which has to do with timestamp expiries. So you can happily use redis like a simple minded fool and it is wonderful. Or you can dig in deeper and only mildly shake your head at some of the command names. But with MongoDB it is just a pain in the ass from the first moment you truly have even vaguely complicated data.

But back to PostgresSQL. The JSON related features are mildly complex but appear to be solving the most common problems. Also by using PostgresSQL it solves the entire debate of relational vs NoSQL. Use PostgresSQL and you can just do both without giving it a second thought. And I for one can certainly say that I have data that demands NoSQL and I have other data that demands relational; all in the same project. But oddly enough the technique that I use is MariaDB for the relational and redis for everything else. This is ideal for me as the relational data is very simple and won't need to scale much whereas the redis stuff needs to run at rocket speeds and will be the first to scale to many machines.

But as for MongoDB, it has been deleted from all machines, development and deployment and will never be revisited regardless of this weeks propaganda.

By substantially new I mean something like the difference between an iPod and an iPhone, that was a huge leap which was actually derided at the time; the general opinion was that apple should stick to music and leave the phones to the big boys like Motorola. My basic point is that each Apple product has faded after a great new leap came out. The macbook business is still huge but pales in comparison to the iPhone business as is the iPod business. So assuming that iPhones will slowly fade at some point, what is going to replace them. Or is apple planning on the iPhone not fading and has no desire for a new product. This would be a huge change from their successful pattern.

I was helping someone with their forgotten iCloud password and we tried a few dozen variations. My incorrect guess was that instead of telling me to go to hell that it was playing some odd game such as letting me try passwords by ignoring me to waste my time.

It simply never occurred to me that this was a gianormous security hole staring me in the face. What exactly is happening at Apple, there is Bentgazi, iOS 8 killing iPhone 4s and iPhone 5, iOS 8.0.1 killing iPhone 6, apparently a last minute screen switch away from sapphire, plus many subtle other things such as it doesn't seem like they are using liquid steel in their cases, and the whole U2 spam crap, which it turns out they wrote a massive cheque to U2 for. Then there is the collective yawn over the iWatch. But worst of all is the total lack of a substantially new product in years. Basically the business model at apple has been to steamroll all their older product lines with something mind-boggling. But they seem to have stalled. iPhone sales are awesome but if you look at the history of all of Apples previous products they basically had their day in the sun and then were eclipsed by the latest and greatest apple product. iMacs, iPods, iPod touches, Nanos, iPhones, iPads, and now the iWatch. I think that the iWatch will end up sitting alongside the Apple TV, not eclipsing anything.

Am I wrong but that this exploit only works if you are running CGI scripts? Am I also wrong in thinking that if you are running PHP as an Apache Mod that this exploit doesn't work unless you are executing command line stuff?

Also the SSH aspect seems to be more of a privilege problem whereby someone has to have a valid ssh account before they can start hacking?

I am going to go out on a limb and say, if you are using CGI you are a dumbass and if you give anyone who you can't trust with ssh then you are also a dumbass. I don't think that I have configured a CGI serving machine since last millennia (literally).

I send all my commands out to /dev/null for extra security.

How many command lines have you copied and pasted into your machine over the years?

In the early days of my Linux fumbling I am fairly certain that I would have pasted a "rm -rf /" as root if it were embedded into other lines of code.

For that matter how many libraries have you downloaded and then run? How would you like it if the latest version of OpenCV came with something that would fry your GPU? Ha ha you were too stupid to check 20 million lines of code to see if there was a GPU frying addition by some guy who managed to get his contribution added at the last second. I hope you learned your lesson? Or is the guy who added it an asshole? (I use OpenCV generically as just some minor library that might not be rigidly managed)

Typed that, looked wrong, changed to bare and then was wrong. Shouldn't have second guessed myself. Also should have thought about bearing arms, or bearing a load. Or just looked it up.

This is a very good suggestions in that it slightly filters reviewers. Except that the restaurant has a limitless supply of these codes. An alternative that I thought of was that you have to use your phone to review the restaurant while standing near it. This mostly prevents hiring shill review mills, and it somewhat limits the reviews to one per device (not terribly hard to get around but a little bit more of a barrier).

What if I dressed up as a doctor, had an air of gravitas, videoed from what looks like an ivy covered university and gave terrible terrible medical advice about Tylenol maximum dosages? Or if I dressed as a garage mechanic used all kinds of mechanical words and gave horrible advice such as sugar in the gas tank eliminates the squeal when you hit the brakes?

We all can't be experts in everything. Some people are really really not technical while not actually being stupid people. This sort of thing might not fool many slashdotters but which fork to use during which course during a fancy dinner with a potential investor in our tech startup might confound many of us; and end up costing us a whole lot more than a replacement phone.