Warming is obviously a lot more complex than CO2 levels, because warming has continued to basically flatline as it has for decades now. So why are we still so concerned about CO2 emissions when the runaway effect predicted is simply not occurring?

There are simply too many natural processes in the earths climate that deal with variances in heat, most variances from other causes are vastly greater than the current minuscule levels of CO2 we see (they are historically high but factor in very little in terms of atmospheric mix).

If we're lucky, we'll get a nice 2C boost for a few hundred years out of all combined warming effects, before sliding into yet another ice age. Sadly I do not think we will be that lucky.

I have Medicaid in Indiana and it's not that bad. I had a $3 co-pay per medicine and now they are telling me they are doing away with it. At one point they paid for eye exams every two years and glasses every two years then they changed the glasses to every five years, but they may change it again. They don't pay for regular teeth cleaning, but they pay for other dental work. I don't know the full scope of the changes.

Hey I get 44oz and even 52oz when I get a free drink at Speedway gas station and I fill it with a mix of Diet Dr Pepper and Coke zero

Hey man, it's Android that's trying to get people to lick phones with the version names.

You can't actually take the sample on the phone - the idea is that you can get your DNA sampled, then the results get stored on your phone - which you can if you wish share that anyone who would like to have it after that, if you choose.

So it's pretty close in terms of value (because if a lot of people do this a lot of researchers could get quick access to DNA data instead of having to do it once per test). But it's not as widespread as direct collection would be.

I don't think I'd want my phone actually being the DNA collection point anyway as it would think I was some kind of human/cat hybrid.

Don't tell anyone, but I'm from the future and wanted to give you a heads up how it goes:

Test 1: Make sure all thrusters installed pointing out.

Test 2: Humans can only withstand how much thrust?

Test 3: Make sure to thrust away from, not underneath, falling debris.

Test 4: Emergency homing signal for safe landing should be changed to not match Arbys drive through wireless mics. "Smoked with real smoke from real wood that's on real fire" ended up being a grimly accurate tagline.

Test 5: Turns out Ed was right and we really do need to add a laser canon for those damn pelicans.

Test 6: Success!

wyoming has radiation?

Hell yes! Have you measured background radiation in the rockies?

communication delays?

Ever tried to maintain cell signal on the way to Yellowstone?

nothing to see, or to do?

Once you've seen Frontier Days once...

No medical equipment?

I go up there all the time with no medical equipment.

I don't know what that gravity would do to your digestive systems.

That's why every astronaut has died immediately after return from space with even less gravity...

I have to break character here and say - you are SUCH a retard. That's enough fun for me. You may carry on if you wish.

Pretty sure you are going to need a drink long before low gravity messes with you.

Pretty much all other reasons you list as problems could be applied to a move to Wyoming, but people do that all the time.

Let's hold a hearing on scientifically driven politics, and don't invite the politicians!

Great, lets just look in on this group of scientists I found that are not funded by government money:

*crickets*

1) The app has to declare if it's going to be doing background processing, and you have to give a reason why they will accept. So not just any app can do that.

What we really need is the ability to turn on and off specific permissions by app. Perhaps with the ability to limit internet permission to certain IPs/URLs per app. That would solve most of the problem.

I thought Google added that ability in an early 4.0 or 5.0 version of Android, but then backed it out... Sadly I think because too many apps react badly when permissions are withdrawn it expects to run. The whole model creates a bad precedent I think where you assume you'll have all the app permissions you requested and so if any are withdrawn individually (which advanced users can do) the app is prone to break even though it could carry on just fine if it had been coded to detect that one permission was disabled. Google is going to have to bite that bullet at some point.

One of the things I was thinking the port was there for, was probably when developers could build native apps for the phone - since it would be a little pokey to ship debug builds and running debug info over wireless to the watch, a development cable would be a great idea.

It's probably also for Apple Store employees to run diagnostics (not sure if they have equipment for that yet).

The diagnostic port is hidden by a cover. I'd be interested to see if removing the cover adversely affect's the watch's water resistance.

It may somewhat, but given that the port itself is located under the round part of the band that slides into the watch, it seems like it would be sealed away fairly well (especially if you designed the strap with that in mind).

It seems pretty sure sweat would not be able to get in there, really only submersion would have a chance.

Excuse me sir, but I could not help heartily agreeing with the veracity of your statement and wondering just why it was your signature for at least that post is not "Ha Ha!".

I agree it would have been really illuminating to do the same test for a large range of free iOS apps.

However I think that you wouldn't see the most egregious of tracking stuff going on in iOS, for two reasons:

1) iOS reviews would I think alarm on something connecting to 810 different tracking sites. Definitely f you were trying to do anything like that in the background.

2) There's simply not as much data to gather. Most Android apps ask for all possible permissions, because why not? You're probably not going to read it anyway. With the iOS permissions as they are the user is going to think "why is this app which has nothing to do with contacts, asking for contacts" (or location, or photo library, or health data, etc).

That said I'm sure many free apps on iOS are doing everything they can possibly get away with, and I would love to see quantified just what that is.