Since my failure to get OpenID working well with my WordPress installation, I’ve decided to start with something a bit simpler, and then based hopefully upon that success build on upwards. So…

Twitter - I’m still not quite sure what the point of Twitter is, but I’m giving it a go. Adding a Twitter Badge to the sidebar was super easy. I just had to cut and paste some HTML from there into my theme’s sidebar.php. I had to add the ‘Follow me’ link at the bottom.

I can now send an update to my own blog from Twitterific on my Mac desktop, or I can send a text message from my phone. Look see! I can micro-blog about my breakfast.

AddThis - The next mini-project is to make my posts easier to share. The AddThis Button seen just below this post, and every post on this blog, allows the reader to share this post with others through any of the popular link sharing systems. I achieved this by downloading and installing a WordPress plugin provided by AddThis… super easy peasy.

FeedBurner - To make my blog easier to subscribe to I’ve published an RSS through FeedBurner. I enabled two things, a link to ’subscribe in a reader’, and a form for subscribing by email. Both were provided as snippets of code to be cut and pasted into sidebar.php. I did have to edit them a bit to make them fit style-wise.

The FeedBurner website provides a lot of configuration options - too many I think. It took me a while to work out how to get to the email subscription page. Anyway, I’ve now subscribed to my own feed, so I have one subscriber. Woohoo!

[...To Be Continued...]

what does this mean?

Well in abstract terms OpenID is an enabling technology that allows an internet user to mediate the flow of their digital identity information between websites. The user establishes a persona URL, like this blog, an identity URL managed by their Identity Provider, then mediates exchanges with other websites, known as Relying Parties, through their browser.

Diagrammatically the parties and network protocol look like this:

Typically, the identity information that is being moved is either assertions about authentication or attributes that contain personal information. An authentication assertion is a cryptographic mechanism for asserting that you are who you say you are, and personal information attributes are things like your first name, last name, email address, etc.

In the context of a blog that translates into the following functionality:

1) The blog authors can log into the blog using their OpenID identifier, rather than remembering a blog specific username and password. So, one less thing to remember.

2) When commenting the blog reader can identify themselves using their own OpenID identifier, and rather than typing in their contact information it can be requested from their profile.

3) The blog author could use the URL of their blog as an OpenID identifier, either by delegating that identifier to another OpenID provider, or by making the blog itself into a provider.

Why do this?

Well, I just wanted to get a hands on appreciation of the state of the digital identity infrastructure available today. So, how do we go about this project? Well, there are resources available on the net, it’s just a matter of bringing them all together. The first step is to establish a digital identity identifier with an identity provider.

Create an OpenID identifier

So, let’s begin with the simple stuff. I created for myself an OpenID identifier at JanRain’s myOpenID service, which is a well known provider. The identifiers it provides are of the form username.myopenid.com, so my identifier is http://merrells.myopenid.com

Delegate a Persona URL to an OpenID identifier

The next step is to delegate the persona URL to the OpenID identifier. This can be done using a WordPress plugin written by Will Norris, called WP-YADIS. Nasty name, but once configured with the name of the identity provider (myopenid.com) and the identifier (merrells.myopenid.com) it will effectively allow me to use my blog URL as my identifier. It does this by adding a couple of link tags to blog web page. You can use View-Source to check they’re there.

Now, when confronted with a request for my OpenID identifier I can type the more personal johnmerrells.com, instead of the slightly less personal merrells.myopenid.com

Let’s test it with http://www.booksiamreading.com . I type in my delegated identifier (johnmerrells.com), and it redirects my to the myOpenID verification page.

It worked. Excellent. But, it would have been nice if the verification page had also displayed the delegation identifier. I wonder if the protocol supports that?

Author/Commenter Login by OpenID

Will Norris, et al, have written a plugin called WP-OpenID, which supports both author and commenter login via OpenID.

Once installed the only configuration requirements are to add the identifier URL for each of the authors.

This is where I’m stuck for the moment. I add my identifier, which I can see has been authorized by my provider, but it doesn’t appear on the admin page. I wonder what’s gone wrong? More investigation is required…

The company name and corporate web pages are somewhat abstract, but it’s clear that there’s something significant going on here from the community forming around their technology platform. Users are free to assemble a collection of applications, called a stack, and publish them for others to make use of, amortizing the cost of their creation and configuration.

In a similar vein is Kimbro Staken’s company JumpBox, which packages single applications as virtual servers. They just raised another round of funding and it looks like they have revamped their website to have that popular three-things-on-the-home-page look. They are focused on solving the problem of getting users from download to running application as quickly as possible, which is a hurdle that users are putting less effort into jumping over. JumpBox gets less attention than they deserve, probably because they’re based out of Pheonix Arizona, where startups are thin on the ground.

Kimbro and I were competitors for a while, back when we were both working on native XML databases, I was working on DB XML and he was working on dbXML. Notice the subtle capitalization difference there!

I emailed the winemaker, Nobilo, and a nice lady there, Jane Bennett, replied:

We worked with our label printers to use this concept on our Nobilo wine labels. Unfortunately, we cannot take claim for inventing the idea. I am glad you liked it though.

I found the label maker, Collotype:

It’s a great idea, but I think they could do with some help with their marketing. “Wine Find ™” is what’s it’s called, with the slightly disturbing sounding tag line of “The silent salesperson”. I couldn’t find any validation or testimonials that it actually works. I wonder if it does…