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:
- or -

When would you want to use one of these instead of  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 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.


  1. AOL needs to decide on, and pick, one ID.  As an identity provider we should be reducing confusion, not increasing it.

    Maybe the one ID we pick is a "landing" page that each user customizes to "advertise" the AOL features they want to tell people about.  Instead of forcing them to use their one of their AOLJournals or Pictures pages.

  2. shadow: I think we should let the user pick what they want to do (while providing a good default that works for most people).  I don't think we want to force you to go customize yet another page.  And I don't think people want to  advertise AOL features; they more likely want to advertise themselves.  Maybe we should let people set up their ID page so that it will redirect wherever they want, including off to their MySpace page, as long as we can verify that they own that other page.  Why not?

    But that's exactly why these are experimental features; play around with them and let us know what you think.  Is it useful to be able to pick from multiple identities depending on what you're doing?  For example if you have a professional profile and also a personal blog (nothing that's secret, just separate from work)?


Post a Comment

Popular posts from this blog

The problem with creation date metadata in PDF documents

Last night Rachel Maddow talked about an apparently fake NSA document "leaked" to her organization.  There's a lot of info there, I suggest you listen to the whole thing:

There's a lot to unpack there but it looks like somebody tried to fool MSNBC into running with a fake accusation based on faked NSA documents, apparently based on cloning the document the Intercept published back on 6/5/2017, which to all appearances was itself a real NSA document in PDF form.

I think the main thrust of this story is chilling and really important to get straight -- some person or persons unknown is sending forged PDFs to news organization(s), apparently trying to get them to run stories based on forged documents.  And I completely agree with Maddow that she was right to send up a "signal flare" to all the news organizations to look out for forgeries.  Really, really, really import…

Why I'm No Longer On The Facebook

I've had a Facebook account for a few years, largely because other people were on it and were organizing useful communities there.  I stuck with it (not using it for private information) even while I grew increasingly concerned about Facebook's inability to be trustworthy guardians of private information.  The recent slap on the wrist from the FTC for Facebook violating the terms of its prior consent agreement made it clear that there wasn't going to be any penalty for Facebook for continuing to violate court orders.
Mark Zuckerberg claimed he had made a mistake in 2016 by ridiculing the idea of election interference on his platform, apologized, and claimed he was turning over a new leaf:
“After the election, I made a comment that I thought the idea misinformation on Facebook changed the outcome of the election was a crazy idea. Calling that crazy was dismissive and I regret it.  This is too important an issue to be dismissive.” It turns out, though, that was just Zuck ly…

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.