I remember one password that I had committed to muscle memory. I burned my hand one day cooking, and had to have my hand bandaged up for a week (note to self: don't try grabbing the steel handle of a pan at 450°F without a mitt). I couldn't type my password from muscle memory with my hand bandaged. I even knew the phrase that it was based on, but after many tries, I couldn't reproduce the exact set of upper and lowercase letters and letter substitutions that I had used. I eventually had to give up and change out all of my passwords and SSH keys, because I just couldn't recover my own password without my muscle memory.
Your interface requires a 3-button mouse, which anyone on a Mac is not likely to have (especially on a laptop). Yes, you can get a right click by doing a two-finger tap, but that's pretty clumsy, and you can't draw with it because that turns into scrolling.
You should probably just let people click on black, white, or grey buttons to select the current color.
Even on a PC - it was a complete nightmare. Opera kept interpreting my right-click movements as gestures and middle button as a request to scroll around the page. It was more than just a little frustrating because of this.
That all said, layout of the site and idea itself is very good.
Before you ask what the minimal code for an HTML5 page is, you have to decide what constraints you are putting. Are you talking about the minimal valid, independent web page? The minimal code that your browser will parse as HTML and generate a DOM for? The minimal code that is allowed in an <iframe srcdoc>?
If you're talking about the minimal valid code for an independent web page, it is:
<!DOCTYPE html><title></title>
The title element is required, and is not automatically inserted if the tags are missing the way <html>, <head>, and <body> are.
If you're talking about the minimal thing the browser will parse, you can provide an empty document (with Content-type: text/html), and the browser will treat it as if it's an HTML document, generating the appropriate elements automatically. It will parse it in quirks mode, but if you don't care about validity, and are talking about an empty document, that doesn't matter much.
If you're talking about what you can embed in <iframe srcdoc>, again, an empty document is acceptable. In that context, the doctype and title are both optional.
Well, that's the thing. They don't know who generated these keys or how. They don't know what the bug is; all they can see is the end result, not how it happened, without talking to the people who generated the keys and investigating the algorithms used, the entropy sources used, and trying to recreate the state of the system at the time the keys were generated.
But without knowing the bug, there is still the enormous vulnerability; pretty much anyone else could do what they have done, crack these keys, and MITM any of the sites that use them.
So, they could have kept quiet, tried to track down who had generated the keys, try to track down how they had generated the keys, and see if there is a problem. But the longer they do that, the more people they'll have to contact, the more likely it is that word will leak out, and the more likely it is that someone nefarious could use this information to their advantage.
By making a big announcement about it, they let everyone know now. Everyone knows to start looking at these keys. They will likely notify any CAs that they can identify of the bad keys that they have found so that they can be revoked (though they have mentioned that finding contact information has sometimes been difficult). Yes, it means that we don't really know how this happened; but it does mean that a lot more people will probably start auditing their entropy sources and pseudo-random number generators to make sure they are working properly.
The DoJ announcement does say "During the course of its investigation of the Google/Motorola Mobility transaction, the Department of Justice cooperated closely with the European Commission."
So yes, it does sound like the Google/Motorola portion of the decision was coordinated. The DoJ was probably waiting for the EC announcement before releasing theirs, or maybe they just agreed to release them the same day and the DoJ one was released a few hours later due to the timezone difference.
It's time zone differences. The 4 hour lag is the difference between Eastern US time during Daylight Saving Time and GMT.
The EC announcement, assuming that the Google blog is on Pacific time, would be around 5-6 PM GMT. That's after normal trading hours ends, which makes sense for announcements like this.
But, BitTorrent Live has nothing to do with BitTorrent, besides the inventor and the name. It's a completely new, proprietary protocol. You need to download their proprietary software to view it. You can't view existing torrents with it; so the Pirate Bay doesn't provide it with a distribution channel.
One of the reasons that BitTorrent took off as well as it did was that it was an open protocol and free software. People could write competing BitTorrent clients. They could extend the protocol, adding new features like trackerless torrents and magnet links.
BitTorrent Live has none of that; it's yet another proprietary streaming service, designed to create a walled garden that the content industry can be happy with. It will succeed or fail based on how well BitTorrent Inc can cut content deals, and cut deals with set-top-box manufacturers to include their software. And that's not really a game that you want to be in, unless you have a lot of leverage like Apple or Amazon, or the backing of big content companies like Hulu.