Even if you've never used the Address Book app this information could be in there. In the OS X first-launch setup dialog it asks for your real name, and that gets automatically inserted into the address book. I'd wager that most people who use Macs have done this, so their real names are accessible to any website using this technique.

Additionally, though this is less likely, if you fill out the registration form during setup I believe that information also goes into the address book, so there's your home address and email too.

http://www.xrez.com/yose_proj/Yose_process.html

I think the markup-parsing part of the HTML5 spec is reasonably stable. Firefox is the first browser to implement the algorithm, so Firefox may have useful feedback for the spec.

You don't need a fast charger at your house; overnight charging will work great using cheaper non-peak power, and will probably extend your battery life vs. fast charging all the time. Fast charge stations can be spaced as sparsely as gas stations.

Gyroscopes don't have to spin. MEMS gyroscopes vibrate instead. They do have moving parts, but the moving parts are insanely tiny, fabricated on silicon chips, and packaged in standard microchip packages. Quite amazing, really, when you think about it.

Net neutrality campaigners aren't just worried about "normal" internet connections, whatever that means. Net neutrality principles apply to *all* internet connections.

This situation is the reverse of the normal network neutrality problem. Normally you would expect AT&T to charge extra for the use of Skype, and that would be a clear net neutrality violation. Having Skype charge extra for using AT&T's network is less bad; Skype is not an ISP and there are many competing VoIP alternatives which do not charge. However, if AT&T is involved in Skype's decision to charge, for example if AT&T is charging Skype directly and Skype is passing that cost on, then it's still a net neutrality problem.

There are tons of translation add-ons for Firefox. The reason it's not built-in is because it's not actually a feature of the browser; it's a web service. Chrome's translation feature works by sending your entire page to Google's translation servers. Mozilla doesn't run a translation server farm; it would be prohibitively expensive for them.

Don't worry, we're planning to make many of the changes customizable. For example, you'll be able to put the tab bar above the address bar or below it. And we're not copying chrome pixel for pixel.

Why are you using this argument to support H.264 rather than, say, Theora? Currently, more users have support for Theora than H.264 (in the HTML5 video tag), because Firefox's marketshare is twice that of Chrome and Safari combined.

Flash includes an H.264 decoder, so moving from Flash to plain H.264 would be an improvement. Whether we want "the perfect to be the enemy of the good" is up for debate, of course.

Flash and H.264 are also "proprietary" in different ways (closed-source vs open-source with patents). Do both kinds of "proprietary" have the same negative consequences?

On the contrary. It is *extremely* rude to throw up a confirmation dialog before every trivial system maintenance task.

As has been pointed out below, System Restore is basically only useful for resolving problems so severe they prevent your system from booting. Once your system has booted you don't really need older restore points, and they take up a *lot* of space. Deleting them is absolutely the right decision for the average user. The *real* problem here is probably the UI for creating system restore points not mentioning the deletion policies and generally misleading people into believing that creating restore points manually is a useful thing to do.

These people creating restore points all the time remind me of the people who get obsessed with defragmenting their disks every night...

No, actually this is a separate effort entirely. This is a product of the same group which produced the "Polaris" 80-core chip, and is meant for research into communication models and memory architectures for massively parallel systems.

Larrabee is still ongoing as a separate project with a different focus. Larrabee is all about getting maximum throughput by adding a wide vector unit with a whole new instruction set to each x86 core. As far as anyone outside Intel knows, the plan is still to eventually release some Larrabee prototypes as-is (with the texture units and everything), and to develop a Larrabee 2 with the lessons learned that can actually compete directly with GeForce and Radeon in the graphics card market.

Indeed; here's an example search showing caption results. I'm just surprised that, of the several articles "covering" this story that I've seen, none have mentioned (even in passing) the applicability of universal captioning to search.