For example, you (or any powerful-enough third party,as you don't even have HTTPS), could anytime throw in any malicious JS code to get whatever data he wants.
And, given that PIN is limited to 4 digits, it's not a protection at all, just a snake oil.
This doesn't solve the privacy issues such as with Facebook and other centralized servers, where you distrust the host as much as hackers or other users.
EDIT: You may want to read this:
http://wiki.appleseedproject.org/doku.php?id=future:encrypti...
Thanks for the link.
If it occurs in the browser, why are the (encrypted) private keys stored on the server? Why not store them in the browser?
They could get around this via an open source browser plugin so that it can be peer-reviewed, or (more desirably) the functionality can be integrated into browsers via the HTML5 spec.
There's no such thing as an Appleseed binary, btw, it's written in a scripted language.
BTW, I'm not trying to imply that these guys have solved the problem -- there are numerous problems, as you pointed out.
Have you read the link I posted about how you could approach encryption at the browser level?
Far from not solving the situation, I think they fall into the category of "half-way encryption is worse than no encryption at all", and they don't seem to understand the social concept of trust. As Jon Callas says, "Encryption is not magic pixie dust that makes everything okay."