Just a note... The broadcast standard currently in use is ATSC 1.0. The new one recently approved is ATSC 3.0. ATSC 2.0 (mentioned in the article) actually died on the vine somewhere.

Err, the time change is this weekend (in the U.S.), seems timely enough to me...

They've been attaching a version number to each one. (Granted, it may make sense to make the version number a little more obvious.) The latest "Creator's Update" is version 1703. The version number is just a representation of the year and month of release.

Could smart criminals just also run a Tor exit node, and just use it to blame anything that they get caught on?

Agreed... I have a 4 year old laptop, high-end so admittedly expensive when I bought it, but it can play today's games without much trouble and they look fine. Yes, some games can't be played at the highest settings, but a lot of games aren't "pushing the envelope" as hard as they used to for graphics. A desktop computer is even easier, you can buy almost any desktop that comes in a regular case, add in a reasonable graphics card and you are good to go, even if the rest of the components are 3-5 years old.

This may be it. I heard an interview on NPR with an ex-NSA guy and this topic came up. He said his advice to the FBI, if he still worked in the government, would be something along the lines of "Bring the phone to the NSA and we will solve this problem for you." He said he had spoken to a number of experts who believed that the NSA has the resources to unlock this phone, but the FBI hadn't asked them, as they were more interested in the precedent than the result.

I found that Airport Utility 5.6 (for Windows --- haven't tried OS X version) can talk to the newer 802.11ac units. While not "supported", all of the options were there and the thing seemed to work fine.

They did this to me too. I used to have Internet and basic cable, and they would regularly call me to try and get me to add phone service. I ended up having the number that they were calling from go directly to voicemail, but from the logs I can see that they continued to call for quite a while.

It says in the article that configuration changes must be made on the WiFi access points as well.

That might be the first thing you would do. Thieves often aren't techies. They'll just boot it up and see if they can get it to work, and then pawn it or sell it to someone else.

If you want to be able to track your machine after it is stolen, just make sure it is easy enough for anyone to get to a web browser (easy-to-find guest account with restricted permissions, but can still connect to the local wifi?). Then run some software like Prey. If you have sensitive data, encrypt it but make sure the machine is still bootable.

Just thought I'd throw this out there since I was just testing it today. I have 802.11n gear (Airport Extreme, the 3x3 version with advertised 450 mbps speed). From 50ish feet away through a few walls I get 8 MB - 10 MB per second to my home server. That's getting up near 100 mbps which is good enough for me on wireless, but obviously nowhere near the 450 mbps that Windows claims my link speed to be.

This is of course normal for wireless networking but I'd hope that 802.11ac gear would be able to do a bit better.

Feedly is cloning the Google Reader API and implementing a new back-end as part of their "Normandy" project, so it's likely that other clients will turn to it to keep their apps working (and synchronized). Naturally, the official Google ones will be left out.

Or maybe they can keep the bandwidth the same (or not lower as much as they could) and instead take advantage of higher quality at the same bitrate... so that the channels don't look so terrible with compression artifacts all over the place.

Mis-interpreted the article title and though that someone was building a supercomputer that is three miles tall. I bet that poses unique challenges too.