OpenSocial, OpenID, and Google Gears: Three technologies for history's dustbin
A poke is not a revolution
Greetings Dr. Falken
OpenID is a federated authentication scheme for the Web. There's all sorts of good shit built into it: identity providers, Diffie-Hellman key exchanges, SSL, and a little bit of HTTP thrown in to make it internet enough. OpenID is very secure, too, because it's a bit like a Rubik's cube: It's complicated by design, so that stupid users and developers don't even bother with it. This makes maintenance of the spec very easy for the OpenID Foundation, which is yet another nonprofit formed around an API.
The point of OpenID was for you to be able to use one account across many web services. And of course, because building off of existing technologies like LDAP, NIS, Kerberos, SAML, XACML, SASL, or Active Directory isn't a good enough excuse for creating a nonprofit, what better thing to do than create a new authentication scheme?
Yeah, the kid who made LiveJournal can surely do a better job than those dinosaurs.
Anyway, have you ever actually tried to use OpenID? I gave it a stab once. What a catastrophe. I got lost on the part where my username isn't really a username. It's aURL, and I have to go somewhere else beyond the site I am trying to log into in order to type in my password. The damndest part of it was I was trying to log into some also-ran Web 2.0 service that thought they would be able to get more users by only supporting OpenID, because shit, 250 million people have an OpenID, by virtue of having an account at Yahoo or elsewhere. The only problem is, only 14 people out of the 250 million even know what OpenID is, and maybe 6 of the 14 have figured out how to use it.
Can you feel the revolution?
Spacely Sprockets or Cogswell Cogs?
The media's fascination with Google taking on Microsoft didn't start with Chrome. No, Google Gears is widely understood to be the first flaccid attempt at an application platform to come out of Wonka's Chocolate Factory. Gears was supposed to be a panacea for web developers who wanted to support offline access of their apps. Well, the user would have to install a browser plugin and the developers need to write code to support less than one percent of their user base, but if you ignore all that shit, Google Gears was the second coming.
The tech media ate that shit up too, proclaiming that this was a "new platform war" and that Google is "driving straight at Microsoft's profits." Gee, does this sound familiar?
Google Gears on its own was a complete failure. Now, though, it's integrated into Chrome. If Chrome can accomplish what no other browser has ever done and overtake IE, Gears will have a shot.
I'm not holding my breath though. Never underestimate the disparity between developer excitement and user apathy.
Storm the Bastille
A revolution doesn't mean that you pseudo-sexually "poke" someone from Facebook to MySpace. It doesn't mean that you can type in your password once and have access to every authenticated service out there. It certainly doesn't mean that you can make a word processor program work when you're not connected to the internet (we've had that feature for decades).
No, a revolution means that somebody gets beheaded. ®
Ted Dziuba is a co-founder at Milo.com You can read his regular Reg column, Fail and You, every other Monday.
Sponsored: Beyond the Data Frontier