<?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: Moving towards an open Facebook (part 2)</title>
	<atom:link href="http://pauljacobson.org/2009/03/13/moving-towards-an-open-facebook-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://pauljacobson.org/2009/03/13/moving-towards-an-open-facebook-part-2/</link>
	<description>blogger.  evangelist.  maven.</description>
	<lastBuildDate>Fri, 19 Mar 2010 08:14:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: pauljacobson</title>
		<link>http://pauljacobson.org/2009/03/13/moving-towards-an-open-facebook-part-2/comment-page-1/#comment-3563</link>
		<dc:creator>pauljacobson</dc:creator>
		<pubDate>Thu, 19 Mar 2009 01:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://pauljacobson.org/?p=2723#comment-3563</guid>
		<description>Hi Chris&lt;br&gt;&lt;br&gt;Thanks for commenting.  I have been thinking about Facebook&#039;s terms and its approach quite a bit more since this post.  I actually did a quick and dirty comparison between Google&#039;s terms of use (I see Google&#039;s terms as a good starting point) and Facebook&#039;s current terms and then also looked at the draft Statement of Rights and Responsibilities and the Principles in a post on my business blog: &lt;a href=&quot;http://webtechlaw.com/where-you-stand-google-and-facebook-comparative-view&quot; rel=&quot;nofollow&quot;&gt;http://webtechlaw.com/where-you-stand-google-an...&lt;/a&gt;&lt;br&gt;&lt;br&gt;The proposed terms of use (for lack of a better term) are very encouraging and the approach Facebook as adopted is very interesting from a lawyer&#039;s perspective.  It is certainly enough to convince me that Facebook may not be the epitome of evil on the social Web.  I reserve that place for LinkedIn which has terms of use that make Facebook&#039;s reviled and retracted terms look tame.  I&#039;ll probably feel even better about Facebook once the current town hall process is complete and the new legal framework is in place but, as I mentioned, it is very encouraging.&lt;br&gt;&lt;br&gt;I would like to see more portability possible, that is to say an opportunity to move more data out of Facebook (I&#039;m thinking specifically about friends list and contact details) but from what I understand in the news lately, Facebook is opening up more and more of its previously closed apis.  That says something too.</description>
		<content:encoded><![CDATA[<p>Hi Chris</p>
<p>Thanks for commenting.  I have been thinking about Facebook&#39;s terms and its approach quite a bit more since this post.  I actually did a quick and dirty comparison between Google&#39;s terms of use (I see Google&#39;s terms as a good starting point) and Facebook&#39;s current terms and then also looked at the draft Statement of Rights and Responsibilities and the Principles in a post on my business blog: <a href="http://webtechlaw.com/where-you-stand-google-and-facebook-comparative-view" rel="nofollow"></a><a href="http://webtechlaw.com/where-you-stand-google-an.." rel="nofollow">http://webtechlaw.com/where-you-stand-google-an..</a>.</p>
<p>The proposed terms of use (for lack of a better term) are very encouraging and the approach Facebook as adopted is very interesting from a lawyer&#39;s perspective.  It is certainly enough to convince me that Facebook may not be the epitome of evil on the social Web.  I reserve that place for LinkedIn which has terms of use that make Facebook&#39;s reviled and retracted terms look tame.  I&#39;ll probably feel even better about Facebook once the current town hall process is complete and the new legal framework is in place but, as I mentioned, it is very encouraging.</p>
<p>I would like to see more portability possible, that is to say an opportunity to move more data out of Facebook (I&#39;m thinking specifically about friends list and contact details) but from what I understand in the news lately, Facebook is opening up more and more of its previously closed apis.  That says something too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: factoryjoe</title>
		<link>http://pauljacobson.org/2009/03/13/moving-towards-an-open-facebook-part-2/comment-page-1/#comment-3562</link>
		<dc:creator>factoryjoe</dc:creator>
		<pubDate>Thu, 19 Mar 2009 01:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://pauljacobson.org/?p=2723#comment-3562</guid>
		<description>I certainly am sympathetic to your skepticism. I agree that Facebook still has much to do to become truly more open — but I think it&#039;s also important to realize that &quot;openness&quot; is largely in the eye of the beholder.&lt;br&gt;&lt;br&gt;On the one hand, they desire to make the service more open for sharing — to make it easy for people to move their content in and out of the service. On the other, there&#039;s open source/web advocates that also want to make sure that the underlying protocols that Facebook uses are interoperable and non-proprietary. Two types of open — both meeting the definition.&lt;br&gt;&lt;br&gt;Still, w/r/t to the legal bit, that&#039;s hard, since most law and terms of services are designed to protect one party over another — especially when Facebook has resources that I&#039;m sure some people would love to have an excuse to sue to gain access to. Openness in business is also something that hasn&#039;t really been done that much before — at least in the consumer web. Facebook gets extra scrutiny because they must match their rhetoric with real behavior, but other web services are equally closed and have perhaps worse or more onerous terms of service by comparison.&lt;br&gt;&lt;br&gt;This is new ground; I believe that whoever figures out this new landscape first will reap a great deal of benefits. The generation of folks working at Facebook seem young and naive enough to dispense with many of the previously &quot;perceived&quot; protections of the past and blaze into the future — but it&#039;s a tall order fraught with challenges and uncertainly. Indeed, time will tell, but I do think that we&#039;ll see Facebook make more overt progress in this regard in 2009 than many other of their competitors.</description>
		<content:encoded><![CDATA[<p>I certainly am sympathetic to your skepticism. I agree that Facebook still has much to do to become truly more open — but I think it&#39;s also important to realize that &#8220;openness&#8221; is largely in the eye of the beholder.</p>
<p>On the one hand, they desire to make the service more open for sharing — to make it easy for people to move their content in and out of the service. On the other, there&#39;s open source/web advocates that also want to make sure that the underlying protocols that Facebook uses are interoperable and non-proprietary. Two types of open — both meeting the definition.</p>
<p>Still, w/r/t to the legal bit, that&#39;s hard, since most law and terms of services are designed to protect one party over another — especially when Facebook has resources that I&#39;m sure some people would love to have an excuse to sue to gain access to. Openness in business is also something that hasn&#39;t really been done that much before — at least in the consumer web. Facebook gets extra scrutiny because they must match their rhetoric with real behavior, but other web services are equally closed and have perhaps worse or more onerous terms of service by comparison.</p>
<p>This is new ground; I believe that whoever figures out this new landscape first will reap a great deal of benefits. The generation of folks working at Facebook seem young and naive enough to dispense with many of the previously &#8220;perceived&#8221; protections of the past and blaze into the future — but it&#39;s a tall order fraught with challenges and uncertainly. Indeed, time will tell, but I do think that we&#39;ll see Facebook make more overt progress in this regard in 2009 than many other of their competitors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
