After my post on OpenSocial, I had no choice but to do some research and sign up with an OpenID provider. Ok, you don't actually need to do any research to get a good OpenID, but I have a complex that won't allow me to make even the simplest of decisions without due diligence. So my choice was MyVidoop, and here's why: browser integration, multi-tier security, and ease and use.
I'm an early adopter; I don't currently use any sites that support OpenID (although most of them are working on it), but what's drawing about MyVidoop is that it handles existing passwords as well. Here's something to think about: I've never trusted the browser to manage passwords for me. Call me old-fashioned, but I've seen way too many spyware horror stories and hacked browsers (and it doesn't help that I'm a Windows user). But at the same time, I've got this exploding array of passwords to keep track of. So how does MyVidoop solve my problem?
Try an integrated browser plugin (supports FF3) that allows me to store credentials remotely. Actually, it gives you the option to go either way, per password: store it locally in an encrypted file, OR store it with your profile on their secure servers. Why am I okay with this? Because MyVidoop protects my information with several layers of security. Step 1 is browser authentication. The very first thing they check is the IP address and browser signature that is making the request to their system. If it's not one that I have verified using one of several alternative methods (email, text message, voicemail), forget about it, you're not getting in. Step 2 is what they call an "image shield." It's a rand
om assortment of images with corresponding letters, three of which make up my unique password token for that session. It's category-based, so you might set it up to be something like Trees, Cars, and Animals. It's a clever and rather powerful authentication mechanism that relies on the classic usability principle of recognition rather than recall.
If you have the plugin, it's a seamless experience. Just log in when you start your browser, and from then on it will auto-populate both username and password fields for any site it knows about. And if it doesn't know about it, it'll ask you if you'd like it to.
The final selling point for me was reading their development blog, which shows how their implementation is secure enough to counter a man-in-the-middle phishing attack that is engineered to exploit OpenID providers. It's a pretty cool walkthrough and you can even mount your own attack to see how it works.




"Accelerators are built on 












