Well holy smokes, this could be the most harmful thing Google have done to HTML5 gaming. I'm going to pester them about it.
While there's not much that can be done for the players themselves, you can probably fix your local copy of Chrome for development purposes: go to chrome://flags and enable 'Override software rendering list'. This should give you GPU-powered WebGL regardless of the blacklist, but don't expect any players to be doing that.
We can force this for node-webkit as well. However we already used to do that, and it broke games on a lot of systems: they'd crash, show nothing but a black screen, or have such severe glitches as to render the game unplayable. The blacklist actually works. It identifies broken systems and gives them a slow-but-works version of the game, instead of fast-but-totally-broken.
So we will still break a bunch of systems that used to work if we skip the blacklist. This is a difficult choice. The best solution is for Chrome to keep a selective blacklist and try to support systems that can still use GPU acceleration on XP and Vista. There's not much we can do other than try to petition Google to bring that back. Or use Firefox!