For example, in the image below, Brad just joined Twitter but has no friends on it. Using the Social Graph API, Twitter could provide Brad a way to find out that his friend Jane is also on Twitter. Here’s how: Brad has linked to his homepage (b3) from his Twitter profile (b1) and also from his homepage (b3) to his LiveJournal blog, Bradfitz (b2). On LiveJournal, Brad is friends with Jane274 (j2), but Brad doesn’t know that Jane274 (j2) also has a Twitter profile (j1). Since the Social Graph API has indexed that Brad and Jane already have declared a public friendship on LiveJournal, it can let Brad know that he might want to add Jane (j1) on Twitter as well.

The main goal for this release was to add URLs as contacts. What does this mean? If you take an URL like http://tantek.com you will see, that his HTML output uses a lot of Microformats – of course, you say 🙂

The great thing about this is, that he therefore makes it easy for NoseRub to get information about him (via hCard) and his web accounts (via XFN). Basically, NoseRub already did exactly that when syncing between different servers. We just need to do some minor changes to allow any URL as contact, but we also added support for the Social Graph API from Google. That means that NoseRub does not only rely on finding information through Microformats on that site, but also uses the data that Google’s API returns for that URL.

Another good example for a great URL as contact is David’s homepage. Working for SixApart, he uses the Action Stream PlugIn for MovableType. The great thing now is, that I can add him as contact on Identoo.com and follow his activities, without forcing him to use NoseRub for himself.

If you hosted your own Twitter, just like you host your own website, you could put your twitter anywhere. Case scenario: I have a twitter blog at dembot.com/twitter All of the friends I follow? How would we connect? You guessed it: RSS!