Tag: openid

For sessions 3 and 4, I attended sessions focusing on social software. From the wiki, session 3 was:

Social Networks – Fred Stutzman. We’ll spend a session talking about Social Networking Websites, such as Myspace, Facebook and Linked In. We’ll look at them, figure out why people use them, and share ideas about how businesses can leverage social networks.

It was attended by what seemed like half campers. Unfortunately, I didn’t really take very many notes during Fred’s session because I was already familiar with his main ideas. There are three main aspects of his thought that he discussed:

1. His Facebook research (It really is fascinating)
2. Situational Relevance:
   Situational Relevance in Social Networking Website
   Situational Relevance and Facebook’s Summer Traffic
3. The Network Effect Multiplier, or, Metcalfe’s Flaw

Most of the discussion focused on situational relevance and the network effect multiplier. to get a good idea of the discussion, you might want to check out the discussion on those posts. I would also encourage you to check out my recent responses to Fred’s thought:

• Comments on “The Network Effect Multiplier, or, Metcalfe’s Flaw”
• Social networking site usage: An explanation for Facebook

Session 4 was on social bookmarking and was moderated by Chris Messina.Chris got the discussion rolling with by explaining his idea of the future of web browsing and his original vision for Flock. He also made arguments for why the future of browsing is currently being developed with Webkit applications.

However, the discussion quickly turned to a discussion of microformats. Fred Stutzman and Terrell Russell or ClaimID (identity management) discussed their implementation of OpenID (universal distributed url login). hCards (like vCards) were also discussed. I had not really understood the idea of XFN before the discussion.

XFN is a simply way to define relationships between people. For example, this is implemented in WordPress when one adds a friend. A typical blogroll implementing XFN could look like this:

<a xhref="http://jane-blog.example.org/" mce_href="http://jane-blog.example.org/" rel="sweetheart date met">Jane</a> <a xhref="http://dave-blog.example.org/" mce_href="http://dave-blog.example.org/" rel="friend met">Dave</a> <a xhref="http://darryl-blog.example.org/" mce_href="http://darryl-blog.example.org/" rel="friend met">Darryl</a> <a xhref="http://www.metafilter.com/" mce_href="http://www.metafilter.com/" >MetaFilter</a> <a xhref="http://james-blog.example.com/" mce_href="http://james-blog.example.com/" rel="met">James Expert</a>

(example from XFN: Introduction and Examples)

It seems like a pretty straightforward evolution of social interaction through the web. It made me wonder why Facebook doesn’t implement this with all of the relationship data they hold. While it might be of limited value in their closed network, the future will (hopefully) allow exporting of data.

We discussed how all of these standards ought to interact in the future. If relationships and identity information were stored as microformats on an OpenID enabled server, it would become possible to export data from your OpenID server to a new service. This advance would make navigating between multiple social applications easier. It would also prevent the need to disclose uneccessary amounts of personal information by uploading ones address book to a new service. This move would both empower the user to take more control of their privacy while automating the more painful parts of joining a new network. My notes for this discussion read:

XFN + OpenID = portable network
XFN + hCard + Jabber + OpenID = ad hoc (open standards) social networks

These formulae certainly stay true to what Chris Messina began by describing as an “Architecture for Collaboration”.

I believe that we closed with a discussion of the privacy implications related to social browsing and microformats.

Technorati tags: barcamprdu microformats