<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Case for Decentralized Social Networks</title>
	<atom:link href="http://manas.tungare.name/blog/the-case-for-decentralized-social-networks/feed/" rel="self" type="application/rss+xml" />
	<link>http://manas.tungare.name/blog/the-case-for-decentralized-social-networks/</link>
	<description></description>
	<lastBuildDate>Tue, 02 Mar 2010 17:35:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sameer Ahuja</title>
		<link>http://manas.tungare.name/blog/the-case-for-decentralized-social-networks/comment-page-1/#comment-8579</link>
		<dc:creator>Sameer Ahuja</dc:creator>
		<pubDate>Mon, 03 Nov 2008 22:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://manas.tungare.name/blog/?p=198#comment-8579</guid>
		<description>The problem as I understand it is that of owning and managing my own social graph across social applications on the web; and the associated problem of managing my data across social applications on the web. Note that the management aspect is as important as the owning aspect. Social connections form from varied contexts. Users have different social graphs at different places, and I do not think that one can assume that users want to &#039;merge&#039; all of them into one universal graph that prevails over the web without having precise control over that graph. 

As you point out, none of the current approaches solves the graph problem (Including OpenSocial, that released after the writing of this article), and its not clear if any of the major social graph providers out there want to solve it either. There are, however, some early approaches: http://www.sixapart.com/blog/2007/09/were_opening_th.html , http://www.dataportability.org/ (I don&#039;t know what the current status of the former is, and the latter is more of an evangelical movement promoting use of open standards). 

Oh, and not to be a nitpicker; but along with XFN, FOAF (http://www.foaf-project.org/) is also one of the viable approaches to represent people and their relationships. Google indexes both for its Social Graph APIs (http://code.google.com/apis/socialgraph/).</description>
		<content:encoded><![CDATA[<p>The problem as I understand it is that of owning and managing my own social graph across social applications on the web; and the associated problem of managing my data across social applications on the web. Note that the management aspect is as important as the owning aspect. Social connections form from varied contexts. Users have different social graphs at different places, and I do not think that one can assume that users want to &#8216;merge&#8217; all of them into one universal graph that prevails over the web without having precise control over that graph. </p>
<p>As you point out, none of the current approaches solves the graph problem (Including OpenSocial, that released after the writing of this article), and its not clear if any of the major social graph providers out there want to solve it either. There are, however, some early approaches: <a href="http://www.sixapart.com/blog/2007/09/were_opening_th.html" rel="nofollow">http://www.sixapart.com/blog/2007/09/were_opening_th.html</a> , <a href="http://www.dataportability.org/" rel="nofollow">http://www.dataportability.org/</a> (I don&#8217;t know what the current status of the former is, and the latter is more of an evangelical movement promoting use of open standards). </p>
<p>Oh, and not to be a nitpicker; but along with XFN, FOAF (<a href="http://www.foaf-project.org/" rel="nofollow">http://www.foaf-project.org/</a>) is also one of the viable approaches to represent people and their relationships. Google indexes both for its Social Graph APIs (<a href="http://code.google.com/apis/socialgraph/" rel="nofollow">http://code.google.com/apis/socialgraph/</a>).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
