Maybe, has Netcraft confirmed it yet?

Disclosing the existence of a vulnerability destroys a lot of its value, too. People who can stop using Tails until the issue is sorted out will do so, shutting off whatever intelligence could be gathered from them. If these guys had a real-world exploitable vulnerability and a willingness to sell it to the NSA, they would have sold it and said nothing.

Only 56.5 acres on land, but 395 million acres downrange.

Yeah, and don't forget that "loud pipes save lives" around typical inattentive drivers. This thing is silent but deadly.

"normal draw is less than 140 watts, put it in standby and get 15 watts"

That's less than 500, but still an order of magnitude more than a set top box should need! IIRC power supply ratings on Apple TV and Roku box are both under 10 watts, real usage is probably 3-5. Add a WD green or similar hard drive (6-8W) and a couple of tuners and encoding ASICS and it still shouldn't break 20 watts at full load.

One device to compromise. If malware infects the LAN-of-things gateway, it can tell your pillows to play deadmau5, tell the lights to flash, and tell the security system to upload shower-cam photos to facebook.

(But then, computer viruses that just annoy the user with sounds and flashing text are deader than dial-up. Connected home malware would probably wait silently for bad weather, then lock you out and demand 0.25 bitcoin to let you back inside, or steal your amazon credentials when the refrigerator orders more milk, or turn on everyone's air conditioner at the same instant to DDoS the power grid.)

More pseudoscience. They say that they're not sure whether this means that porn shrinks your brain, or if the shrunken brain causes porn viewing. But, this leaves out the very real possibility that this correlation means nothing whatsoever. The site below collects correlations that look pretty convincing in the graphs, but quite obviously are unlikely to be cases of causation in either direction:

http://www.tylervigen.com/

If the misclassification only occurs on rare inputs then any random perturbation of that input is highly likely to be classified correctly.

The fix therefore (likely what occurs in the brain) is to add noise and average the results. Any misclassified nearby input will be swamped by the greater number of correctly classified ones.

This will actually help!

First, voice doesn't use that much data. For example, Viber (a popular VOIP app) uses 0.5MB/min which would be about 0.5GB for 1000min.

More importantly, once every one is transitioned off 3G onto 4G/LTE (i.e. VOIP over LTE) the carriers can repurpose the 3G spectrum for 4G and thereby gain more 4G/LTE capacity.

Because I already have one Facebook profile, and it's more than enough. I don't want to have to maintain another one just to keep rating Android apps or commenting on Youtube cat videos.

The deal doesn't make sense to me, but presumably it would involve Dr Dre and Jimmy Iovine being contracted to stay for some minimum amount of time, which brings a lot of clout (esp. Iovine) in the music biz.

The $3.2B price if true seems insane though. Between 2012 and 2013 Beats bought out HTC's 50% ownership for a total of $415M (25% in 2012 for $150M, 25% in 2013 for $265). So, if half the company is worth $415M, the whole thing should be worth closer to $430M, not $3.2B!

It could be cleverly disguised as a bit of MD5 but is actually something encrypted with a 33 character one time pad.

And the civilian world isn't prepared for a zombie apocalypse either, or to be suddenly attacked by hoards of man eating tigers.

Is this a slow news day?

"Yes, we can trace the changelogs in the software & note who was checking the changes and missed them, but that all can be circumvented."

Actually it can't. That's kind of the point of git.

"The fact is we don't know if Heartbleed was an honest mistake or not...we don't know who knew and when..."

We do know who and what and when, because the person who wrote it and the person who signed off on it have commented publicly about the bug.

Maybe you're thinking of Apple's "goto fail" SSL exploit where we really don't know who or what or when and probably never will because it's not likely Apple is going to release their RCS logs.

This technique works best when combined with cold fusion. Also, don't forget about step 3.