Skip to main content

Your blog is your OpenID

As of this morning's Journals update, you now have a couple of new choices to use for your OpenID:
http://journals.aol.com/screenname
- or -
http://journals.aol.com/screenname/blogname

When would you want to use one of these instead of http://openid.aol.com/screenname?  It depends on what you're doing.  If you're leaving a comment over on a LiveJournal, you may want to point back at your blog so they can come and comment on yours.  This lets you do that in a verified way.  If you have more than one blog, the first URL gives a synopsis of all your blogs, and you may want to hand that out instead.  These are for experimentation only at this point and may change, so please don't use one of these for a permanent identity quite yet.  They both delegate to http://openid.aol.com/screenname so all three are effectively transparent aliases of each other.  Which one you use is up to you.

Another subtle change:  When someone comments on your blog, their screen name now links to a search for their AOL Journals.  So when you click on their signature, you can get to their list of blogs if they have any.  This makes it slightly easier to go back and comment on their blog.

We're also experimenting with hCard support.  The signatures on entries are marked up so that hCard processors will pick up on the fact that they name a person that has a URL -- and that URL is an OpenID.  We don't do this for comments yet.  I think we'd want to give commenters control over how much information gets published about them.  Combining this with OpenID opens some very interesting possibilities.  People who opt in would be able to verifiably link their comments across OpenID-enabled sites, automatically track responses to their comments, or find other people who write similar comments.  And a lot more things I haven't thought of.

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.