Yeah, yeah. The sky is falling.... Except that it isn't. With signed bootloaders like shim, you can install or run any operating system yourself without changing the BIOS to disable Secure Boot at all.

Not being able to run a 3rd party OS was a concern with Windows 8. But the open source community have solved that problem. So being able to disable Secure Boot is no longer required.

That's exactly my point. You could have voted 1,2,3,4,4 previously. Since you didn't indicate a preference between the last 2 candidates, it would stop counting at that point and leave everyone else's vote to decide which of the remaining two gets in. While leaving the opportunity for your vote to count against one of the first three candidates. But now you can't do that.

He's being quite literal there. Valve doesn't force people to work on particular projects. If nobody wants to do it, it wont get done.

I don't want my forth choice getting in. At some point I might want to waste my vote instead of having it count towards the lesser of two evils. But the system in Australia doesn't allow for that (anymore).

Here in Australia they keep complaining about wasted votes, without giving the population a way to explain why they don't want to vote. People should either fill out a ballot, or a short form to indicate why they don't want their vote to count.

Only allow one sided transactions that create new tokens to be signed by the reserve bank's key. Partition transactions into separate chains based on transaction hash. Validate the "official" blockchain in large data centers. Offer API access to submit or verify transactions without fetching the entire chain.

It really shouldn't be difficult to design the basic software changes to the bitcoin client. Scaling across a data center might be a bit more work though.

Those results are DMCA'd fairly frequently, though the DMCA details are helpfully listed with the links that were blocked...

Are you insinuating something?

When Microsoft added their "you downloaded this" attribute that warns before executing the file, they implemented it badly. They should have copied the unix default that files are not executable until they are marked that way. I mean they could have used their existing "executable permission" on the entire drive, then prompt the user to change the permissions on each file individually. Including a UAC prompt if they need to enter some admin credentials to make it work.

Oh, well. It's exactly what I expect from Microsoft anyway.

So the real take away is that they have no idea how much of this 1.2 PB is actually child porn. What they have is a file sharing / web hosting service with 1.2 PB of data, provided by users, some of which they know is child porn.

Sounds like an interesting idea to increase capacity, but the downsides are huge. This really needs filesystem level optimisations to get any performance out of it. For rarely modified bulk storage, this should be fine.

The memory of the device contains all of those precious keys they are worried about getting into the hands of evil hackers. While I'm fairly certain blu-ray has been broken for a long time, mostly by grabbing the keys from software players. This adds another avenue to discover valid keys from any player.

MMT? They have some ideas I would agree with, but they don't recognise the current importance of the banking sector IMHO. Though government spending is important, it's the banking sector that has created most of our spending power by issuing loans. I'd like to see that balance shift back towards fiat currency in the future, but we need a working model of the actual economy. A model, consistent with the practice of double entry book-keeping, that is capable of predicting our most recent crisis and warning about the next one.

Krugman thinks that banks are mere intermediaries between patient people and impatient people. Have you ever seen your bank balance drop when the bank creates a loan?

A dumb watch has a hardware logic circuit to drive a segmented display. A smart watch has a general purpose CPU that has to render the time using a supplied font to the pixels of the display. This might be just a blit from a pre-rendered buffer, so long as the fonts align to the pixel grid. But even with a "paper" screen, the CPU is *always* going to be an order of magnitude more power hungry than a hardware implementation.