Skip to main content

How many different identities can one person sanely manage?

...asks John Udell, in Critical mass and social network fatigue.  I'd argue that the answer is about one and a half, in the long run.  (The Shockwave Rider pushed it a lot further, but then he was founding cyberpunk.  Also, he was fictional.)

When "identity" was just basically a system-local nickname used between you and a service, having multiple names for yourself was a minor inconvenience at worst, and sometimes mildly useful for privacy.  Now that the services are more and more intermediaries between people, nicknames are a problem.  Jon notes:
Years ago at BYTE Magazine my friend Ben Smith, who was a Unixgreybeard even then (now he’s a Unix whitebeard), made a memorablecomment that’s always stuck with me. We were in the midst of evaluatinga batch of LAN email products. “One of these days,” Ben said in, Ithink, 1991, “everyone’s going to look up from their little islands ofLAN email and see this giant mothership hovering overhead called theInternet.”
Yep.  Email is still the killer app of the Internet, and it wouldn't be if it were still stuck in LAN mail silos.  Though spam is now so bad that I literally can't send email to a few people who can't manage their spam filters.  That's a real issue and represents a real opportunity as well.

While OpenID isn't a total solution for these issues, it's a critical piece of infrastructure.  As an example of the kinds of things it enables, take a look at Jyte.

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

XAuth is a Lot Like Democracy

XAuth is a lot like democracy:  The worst form of user identity prefs, except for all those others that have been tried (apologies to Churchill).  I've just read Eran's rather overblown "XAuth - a Terrible, Horrible, No Good, Very Bad Idea", and I see that the same objections are being tossed around; I'm going to rebut them here to save time in the future.

Let's take this from the top.  XAuth is a proposal to let browsers remember that sites have registered themselves as a user's identity provider and let other sites know if the user has a session at that site.  In other words, it has the same information as proprietary solutions that already exist, except that it works across multiple identity providers.  It means that when you go to a new website, it doesn't have to ask you what your preferred services are, it can just look them up.  Note that this only tells the site that you have an account with Google or Yahoo or Facebook or Twitter, not what the…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.