Here are ALL TEN global data sets included in one graph. Every single one shows warming. Can you seriously look at that and still claim no warming over the last 18 years?

-

That is the same idea, but worse, than a large screen panel with a camera facing the other way.

The simple fact is that the surface of a 3D shape can't be made to show the path of light through every part of that shape from every angle simultaneously without bending light.

Either it can only do so from one angle at once, meaning any other angle is inneffective, or it can show all angles through a point, and any other point is inneffective.

Whine whine... the people complaining this character or that character is overpowered. Quit whining that everything has to be NERFED just because you suck and you lost the battle. The Superman character comes with a sysop root account on the game server. So what? Deal with it and quit whining.

-

They know this is an issue they'll win in the long run. There is no justification for the states doing what they are doing, they've just been paid off by the auto dealers. Tesla has won every fight about this I'm aware of. So they want it, they want to get this straightened out in the courts.

If you try to do something to skirt the law, you risk it biting you in the ass later. If you get a court ruling saying "You are allowed to do this, the state has to F off," then you are good to go.

Also, you might notice it gets them press. Nothing like looking like the poor trod on underdog to get more people sympathetic to your cause an interested in your product. They go about everything above board, get stepped on, fight back, win, and then get their way, plus good PR.

Have to take the long view on these things.

Correct. They adopted that statement (or a substantially equivalent statement) back in 2007.

Prior to that, they had a denialism statement. As I said, American Petroleum Geologists were the last scientific body of national or international standing to offer any hint of support to climate denialism.

There are many scientific bodies in unrelated fields that have never commented on the subject. There's the American Petroleum Geologists and perhaps some others with statements that carefully dodge having a position, but there's not one scientific body of national or international standing opposed to the effectively unanimous agreement by climate scientists that Global Warming is real and that it is directly a result of CO2 and other man-made causes.

-

Let me help you with that.
Here is the graph you're looking for, showing continuous cooling trends from 1965 to 2013.5

The bottom line is that you have given absolutely no rational reason for ignoring vast bodies of data proving your assertion is false.

You eagerly embrace the RSS graph for the sole reason that, on this arbitrarily selected time interval, it happens to give a linear trend line with a small enough warming to dismiss as negligible.

I asked if you had an rational reason from selecting the RSS data set, and you had none. I asked what you would do if I selected a different time interval, one where RSS showed warming and UAH didn't. You did not deny that you would have irrationally reject the RSS dataset and irrationally latched onto the UAH set.

You are flatly ignoring a MULTITUDE of global surface data sets showing the earth has in fact warmed over the last 18 years.

You have flatly ignored the ocean data set, a data set which you have not contested carries 45 times more weight than any atmospheric data. A data set which reflects 90% of the climate warming as opposed to the 2% warming that happens in the atmosphere. A data set which shows a perfectly steady warming rate for many decades. A data set which shows there has been absolutely zero slowdown in warming over the last 18 years.

You ignored virtually the entirety of data. You latched onto one cherrypicked fragment that most nearly fit what you wanted to find, tailored to this utterly arbitrary 18 year example. You have given no rational reason for latching onto this cherrypicked datapoint.

Can you really not see that this is a textbook case of Confirmation bias?

Can you really not see that what you have just done is exactly what I did in the 1965-2013.5 graph I linked above?

-

"I'm still waiting for an example"

So, instead of doing what everyone else did and look up what was vulnerable and how shell shock could be exploited in SSH (which NIST specifically mentions), you chose to make up a bullshit idea about how it could be exploited that conveniently fit your "holier than thou" attitude about security and argue from ignorance about the exploit.

Good call.

Article:

The new work is interesting and important, but its primary significance is that it makes future work distinguishing the possible alternatives more challenging. It's also interesting because unlike the other two proposed mechanisms it is a result of the fundamental asymmetry in the weak force rather than an accidental boundary condition, so it implies that life everywhere is more likely than not to be right-handed, whereas the explanations involving magnetic fields will make a universe that's 50/50 right/left.

I'm not sure why you felt the need to blame the victim on this, but the reality is that this is a problem not because of lax security measures on the part of server maintainers, but because it allows attackers to bypass good security measures if the shell being used is Bash.

And, because the exploit makes services such as SSH vulnerable, it can be used even if normal modes of passing data to the server are sanitized.

No kidding. The whole reason there's a time between "due" and "late" is so that you've time to get a payment out and deal with any issues. Hence it behooves you to pay when something comes due, or shortly after, rather than wait.

Like one time I get a call from some business who just got a check from me to them by mistake. It was for my association dues. My bank mails out a cashier's check, at my behest, each month to the property manager. They had done so properly, but the USPS fucked up and sent it to the wrong address. Now this was no issue as I still had 25 days until payment was late. So I called the bank, they voided the first check and issued a new one. Everything got there no problem.

Now had I waited till the last second it would have been ok, I wouldn't have been out of house and home or anything, but it would have been a hassle getting things all straightened out, and I might have had to pay a late fee. Probably not, as they need to be nice to the owners since we hire them, but they would have the right to charge it.

You want to build slack in to your schedule in case something goes wrong, and that applies to finance as well as it does travel or the like. Well, that time between "due" and "late" is the slack.

It's that simple. Even with the patches, bash is still running the contents of environment variables through its general command parser in order to parse the procedure. That's ridiculously dangerous... the command parser was never designed to be secure in that fashion. The parsing of env variables through the command parser to pass sh procedures OR FOR ANY OTHER REASON should be removed from bash outright. Period. End of story. Light a fire under the authors someone. It was stupid to use env variables for exec-crossing parameters in the first place. No other shell does it that I know of.

This is a major attack vector against linux. BSD systems tend to use bash only as an add-on, but even BSD systems could wind up being vulnerable due to third party internet-facing utilities / packages which hard-code the use of bash.

-Matt

Any program that a) listens on a socket and b) calls out to a shell with an argument partially constructed from user input is vulnerable if the shell is unpatched bash. Apparently DHCP does this: https://www.trustedsec.com/sep...

The only saving grace in this bug is that it's relatively easy to patch on client and server machines.

But there are a lot of things that aren't client and server machines that run linux and use bash. Routers, cable modems... all kinds of embedded systems. These things generally lag behind everything else. Firewalls will no-doubt be getting upgraded as we speak, but routers? Ultrasound machines in hospitals?

There is a lot of hard-to-patch hardware out there, and while I'm sure manufacturers are working on getting fixes out, it's going to be a long, hard, expensive process to ensure they're implemented.

We're incredibly fortunate that this bug is pretty easily fixable, but there may well be additional lurking issues, and there is always the chance we are going to find something that can't be easily fixed without breaking existing bash functionality. The probability of that is low, but the consequences would be enormously bad.

We've all heard the saying, "If builders built buildings the way programmers wrote programs the first woodpecker to come along would destroy civilization." This has given us a glimpse of what a woodpecker might look like.

Which makes it an excellent dev environment, but terrible for production use...
While you want your code to be able to cope with database instability, when that code goes into production you also want to minimise the chances that it will ever have to.

I wouldn't presume reporters did their job, they rarely do these days. It is amazing how lazy most reporting is. I generally assume when you hear a story with no discussion of it that all they did was get that person/company's story and print it and did no checking. Usually, I'm right in that :P.

While I'm not saying we should take the word of the lenders without verification, neither should we take the word of the people who are on the receiving end. They may very well not be telling the whole story. Some people who have financial troubles have them because of their own choices, but they rarely admit it.

I had a roommate like that. He was an alcoholic who wouldn't admit it or deal with it. He continually made bad choices in his life, but would never admit anything was his fault. In terms of finance he never paid things when they came due, he didn't pay until he was forced to. It was "due" according to him when they were about to shut off his service, or the like. So he'd get mad about his cellphone getting shut down when he was "a day late" by which he really mean "45 days past the due date, over 30 days late, and had 2 threatening letters to disconnect."

So before you go jumping to the defense of the people in the article, you might want to see what the terms of something like this is. I don't know, and I'm not saying it isn't a "you have to pay by the second it is due or we shut it off," but it also might well be a normal "It is due on day X, late on day X+15, and we shut it off on day X+20," and the people involved have just decided that "X+20" is the day it is "due".

With regards to #2, where in the US if you call 911 do you not get an ambulance? They are not taxpayer funded, but they are required to take ALL calls. If there's a medical emergency, you'll get transport and treatment, even if you lack the means to pay. That is part of the problem with high healthcare costs (the costs of people who don't pay get rolled in to the people who do) and an excellent argument for universal healthcare at least for emergency treatment.