While Kinloss is certainly quite far north, you have to account for the warming effect of the ocean and particularly the gulf stream. Scotland is more wet than cold as a result, with the average low being above freezing year round.

I don't know how big an issue cloud cover and rain would be, but the temperature associated with latitude is probably less of an issue. The latitude itself isn't far off that of the Kodiak Launch Complex in Alaska.

The summary was quite lacking. For those not wanting to rtfa, here's what it says under why broadcasting the blockchain in a way that can be picked up by low cast receivers is or might be useful. An AC post below also mentions that TV coverage may be better than mobile internet coverage.

This scheme makes it easy to construct affordable receivers that do not need mobile data connections in order to follow bitcoin traffic and to react to the received bitcoin payments. This would make it possible to build bitcoin counterpart for cash payment terminals, anything from a cash register to a coin operated self-service laundry. If the receiver application follows only transactions relevant to itself, it will be possible to build it using even an ARM microcontroller.

Also, it allows an alternative way to access the bitcoin network in cases where only a very low speed Internet connection is available. And, for all the tin foil hat wearers out there, this is a way to connect to bitcoin network without a trace! You only need online access when you want to make transactions yourself.

The data stream can contain other information, such as exchange rates between bitcoins and traditional currencies.

Of course linux is targeted. There are large numbers of linux servers, with fast processors and very fast high capacity network connections. Making matters worse, because they often to run important services, people may be slower to upgrade packages/kernels.

I don't know about this particular botnet, but it's been a long time since saying "I don't run windows" counted as a security strategy.

Fifteen years ago, you opened the yellow pages for the same information. Did you say then, who controls this book? Did you worry about all the power being in the hands of a single phone company?

Likely not, and for two reasons. If the phone company abused it, they'd lose the trust and goodwill that makes the very product valuable, and if it was no longer accurate someone else would come alone and make an accurate version.

Why is that not the same for Google? If their maps become unreliable, won't people move to Bing? If not, why not?

Misleading headline: FDA != NIH.

Guessing you never read the article. Had you done so, you would have seen this bit:

"[E]mployees discovered vials labeled ”variola,” commonly known as smallpox, in an unused portion of a storage room in a Food and Drug Administration (FDA) laboratory located on the NIH Bethesda campus."

And yet, wouldn't a pilot who left the cockpit while the plane landed using instruments be fired?

I get why I'd want to do it at home, but not why I'd pay someone else to do it

I'm not sure how you're going to create an asthetically pleasing multi color 1,000 lumen LED that fits in a standrard lamp using a $10 controller. Plus create an app or web interface to control timing/dimming/color. If you figure it out, please post the details as I'm sure lots of folk would love to take on that project.

In the meantime, I'm thinking these look pretty neat if a little expensive since I think you'd need quite a few bulbs for the best effect.

Seems it is about operating beyond the permitted frequency and power:

13. The Commission’s investigations found that most 5 GHz devices are manufactured to enable operation across a wide range of frequencies, extending down into the 4 GHz bands and up to almost 6 GHz. The devices are controlled by software that manages the specific parameters used in the
equipment. In most of those cases for which a specific cause was determined, the harmful interference was the result of third parties or users modifying the software configurations to enable operation in frequency bands other than those for which the device had been certified, but without meeting the technical requirements for operation in those frequency bands (such as the U-NII-2C band where interference to the TDWR was occurring).

So a hardware limit to prevent out of band operation would solve the problem; while allowing the software to be controlled by the user. I've no idea how difficult a hardware solution would be, and I can see why it would be more expensive than a software one. If this has been abused, I can see why the FCC would be seeking such a ruling.

Presumably only on the U-NII bands, to 802.11a. Other devices would be unaffected by a rule affecting U-NII

I guess this is to prevent software modifications that may be able to increase the power output of a device beyond that permitted by the FCC?

He doesn't really blame Google. From the article:

To be fair to Google, it opposed the European court ruling.

He does question why there's no apparent right to appeal. It would certainly seem reasonable to allow the person responsible for an article to highlight why it is still relevant or not outdated since often they will have better knowledge of the subject area than a paralegal.

Unless O'Neal becomes famous and therefore relevant for exercising his right to be forgotten?

Are you serious? The applications exist for when you have access only to a computer and a browser. it doesn't matter what operating system it runs, it doesn't (or shouldn't) matter what browser it running. It doesn't matter that you have no admin rights. If you need to edit a document, it should just work.

There's also no indication that other carriers are immune from this problem; and unlike t-mobile, other carriers are still collecting these charges.

Sounds like you want to compare the cheapest android devices with the most expensive apple ones. The more expensive android devices are much more likely to keep getting updates. And if they're a Google branded device, even when official updates end there's a community to support it. That's why a four year old Nexus One can run Android 4.4 today.