<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/">

<channel>
	<title>Open Parenthesis &#187; Ownership</title>
	<atom:link href="http://www.openparenthesis.org/tag/ownership/feed" rel="self" type="application/rss+xml" />
	<link>http://www.openparenthesis.org</link>
	<description>Because these are the early days of a long revolution . . .</description>
	<lastBuildDate>Mon, 30 Jan 2012 16:13:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Facebook Comments Box, Ownership</title>
		<link>http://www.openparenthesis.org/2009/04/14/facebook-comments-box</link>
		<comments>http://www.openparenthesis.org/2009/04/14/facebook-comments-box#comments</comments>
		<pubDate>Tue, 14 Apr 2009 15:50:57 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[comments]]></category>
		<category><![CDATA[Comments Box]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[Facebook Connect]]></category>
		<category><![CDATA[Ownership]]></category>
		<category><![CDATA[Social]]></category>

		<guid isPermaLink="false">http://www.openparenthesis.org/?p=1191</guid>
		<description><![CDATA[I&#8217;ve been looking into the Facebook Comments Box, which launched in February. Photo by suburbanslice It&#8217;s a perfect example of what I&#8217;m seeing as a growing trend, in which various &#8220;social widgets&#8221; actually replace functionality which should be built into the platform hosting the site. Bundling together the ability to use your Facebook identity with [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been looking into the Facebook Comments Box, which  launched in February. </p>
<div id="attachment_1197" class="wp-caption alignright" style="width: 275px"><a href="http://www.flickr.com/photos/suburbanslice/2957144071/"><img src="http://www.openparenthesis.org/wp-content/uploads/2009/04/objection.jpg" alt="Photo by suburbanslice" title="objection" width="240" height="180" class="size-full wp-image-1197" /></a><p class="wp-caption-text">Photo by suburbanslice</p></div>
<p>It&#8217;s a perfect example of what I&#8217;m seeing as a growing trend, in which various &#8220;social widgets&#8221; actually replace functionality which should be built into the platform hosting the site. Bundling together the ability to use your Facebook identity with the actual management of comments themselves looks like progress but I think it&#8217;s really a step backwards. </p>
<p>Announced on the <a href="http://developers.facebook.com/news.php?blog=1&#038;story=198">Facebook developer blog</a>, the Comments Box widget is embedded into your site through javascript, and basically enables Facebook-driven commenting.</p>
<p>Facebook users can leave comments using their Facebook identities, and when they do will also have the option to publish those comments back to their Facebook profiles. (This is already possible using the Facebook Connect APIs, but the comment box certainly simplifies the process). </p>
<div id="attachment_1194" class="wp-caption aligncenter" style="width: 335px"><a href="http://developers.facebook.com/news.php?blog=1&#038;story=198"><img src="http://www.openparenthesis.org/wp-content/uploads/2009/04/commentsbox-300x184.png" alt="Facebook Comments Box" title="commentsbox" width="300" height="184" class="size-medium wp-image-1194" /></a><p class="wp-caption-text">Facebook Comments Box</p></div>
<p>What happens in the process, though, is that all your comments on your blog are no longer really on your blog. Those comments are actually submitted to Facebook, who stores them for you and shows them on demand when your pages containing the comment box load. </p>
<p>In WordPress terms, this means you&#8217;re not able to use <a href="http://wordpress.org/extend/plugins/akismet/">Akismet</a>, or <a href="http://wordpress.org/extend/plugins/wp-mollom/">Mollom</a>, or <a href="http://wordpress.org/extend/plugins/openid/">OpenID</a>, or <a href="http://wordpress.org/extend/plugins/wp-recaptcha/">ReCaptcha</a>, or any of the other plugins you might be using on your site to manage comments. (You also won&#8217;t be able to use the WordPress iPhone app to moderate comments, since they aren&#8217;t submitted as comments to WordPress). </p>
<p>It also means that someday, when you decide to migrate away from the Facebook Comments Box, there&#8217;s no simple way to get all the comments out (and it isn&#8217;t clear whether the terms of service would allow you to do so even if it were simple). </p>
<p>The announcement is careful to note that:</p>
<blockquote><p>The Comments Box allows non-Facebook users to make comments on your site as well.</p></blockquote>
<p>But that feels a bit like &#8220;we&#8217;ll still allow you to use cash, even after we install the credit card machine&#8221; &#8211; it&#8217;s giving me back something I already had as though it were a bonus. It&#8217;s as though we&#8217;re at the point where &#8220;non-Facebook users&#8221; are, like &#8220;those with JavaScript disabled,&#8221; a community we magnanimously allow to continue to use the web but don&#8217;t really design for. </p>
<p>Like <a href="http://developer.yahoo.net/blog/archives/2009/03/js-kit_updates.html">Yahoo Updates with JS-Kit</a>, <a href="http://www.typepad.com/connect/">TypePad Connect</a>, <a href="http://disqus.com/">DISQUS</a>, and <a href="http://intensedebate.com/">IntenseDebate</a> (though the last of these offers a comment import/export feature), this is yet another &#8220;all ur comments are belong to us&#8221; move, in which I think the hosting site loses more than it gains. </p>
<p>Or am I just a crusty old first-generation blogger thinking that I need to store away comments in a database I control, and I should really be more open to having my comments streams &#8220;in the cloud&#8221;?</p>
<p>See also:</p>
<ul>
<li><a href="http://www.readwriteweb.com/archives/facebook_launches_commenting_widget.php">Facebook Launches Commenting Widget</a></li>
<li><a href="http://mashable.com/2009/02/19/facebook-comment-box/">Facebook Connect Adds Cut-and-Paste Comments Widget</a></li>
<li><a href="http://blog.perfectspace.com/2009/02/20/facebook-comment-widget-quick-review/">Facebook Comment Widget: Quick Review</a></li>
<li><a href="http://arstechnica.com/web/news/2009/02/facebook-invades-your-blog-rest-of-web-with-new-comment-box.ars">Facebook invades your blog, rest of Web with new Comment Box</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.openparenthesis.org/2009/04/14/facebook-comments-box/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
	<enclosure url="http://www.openparenthesis.org/wp-content/uploads/2009/04/objection.jpg" length="14690" type="image/jpeg" /><media:content url="http://www.openparenthesis.org/wp-content/uploads/2009/04/objection.jpg" width="240" height="180" medium="image" type="image/jpeg" />	</item>
		<item>
		<title>Type Pad (dis)Connect &#8211; All UR comments are belong to US</title>
		<link>http://www.openparenthesis.org/2008/12/02/type-pad-disconnect-all-ur-comments-are-belong-to-us</link>
		<comments>http://www.openparenthesis.org/2008/12/02/type-pad-disconnect-all-ur-comments-are-belong-to-us#comments</comments>
		<pubDate>Tue, 02 Dec 2008 17:53:12 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[Blogging]]></category>
		<category><![CDATA[comments]]></category>
		<category><![CDATA[Connect]]></category>
		<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Ownership]]></category>
		<category><![CDATA[Social Web]]></category>
		<category><![CDATA[Type Pad]]></category>

		<guid isPermaLink="false">http://www.openparenthesis.org/?p=809</guid>
		<description><![CDATA[In some ways it is exciting to see the launch of Type Pad Connect but in others it seems a Faustian bargain. You get some spiffy features, including the ability of other bloggers to leave comments (which appear to be) on your site using OpenID, with threading, and with avatars; but in the process you [...]]]></description>
			<content:encoded><![CDATA[<p>In some ways it is exciting to see the launch of <a href="http://www.typepad.com/connect/">Type Pad Connect</a> but in others it seems a <a href="http://www.bartleby.com/59/4/faustianbarg.html">Faustian bargain</a>. </p>
<p><a href="http://www.typepad.com/connect/"><img src="http://www.openparenthesis.org/wp-content/uploads/2008/12/typepad_connect.png" alt="" title="typepad_connect" width="500" height="352" class="aligncenter size-full wp-image-815" /></a></p>
<p>You get some spiffy features, including the ability of other bloggers to leave comments (which appear to be) on your site using OpenID, with threading, and with avatars; but in the process you put all your comments (and your relationship with your blog readers) in someone else&#8217;s hands. </p>
<p>It also seems like the real benefits of using TypePad Connect come from network effects &#8211; once everyone has a TypePad Profile and every blog uses it for comments, the benefits will be great. But what about when only some of your users have TypePad profiles, or want TypePad profiles? What about letting people comment with identities they already have rather than creating yet another profile / lifestream?</p>
<p>Ok, so maybe the title&#8217;s a bit strongly worded, and if you&#8217;re already using a hosted blog, or using TypePad for blogging, maybe it doesn&#8217;t where your comments <strong>actually live</strong>. But I don&#8217;t think it will work for me. </p>
<p>What is TypePad Connect? It&#8217;s basically a drop in replacement for however your blog current handles comments &#8211; you swap out how you currently handle comments and use TypePad Connect instead. </p>
<p>Why would you do so? </p>
<p>TypePad Connect Benefits for Bloggers:</p>
<ul>
<li>Enables you to accept comments from users with OpenIDs or TypePad Connect Accounts, whether your blogging platform accepts OpenID or not</li>
<li>Provides threaded comments, with avatars (for users who have TypePad Connect accounts)</li>
<li>Links comments to profiles of the people leaving them (for users who have TypePad Connect accounts)</li>
<li>Enables you to moderate and reply to comments via email</li>
<li>Enables you to manage comments from multiple blogs in one place</li>
</ul>
<p>What about blog readers? (Forgetting for the moment that many blog readers are also blog authors)</p>
<p>Benefits for users:</p>
<ul>
<li>OpenID. If you don&#8217;t have an OpenID, you can sign up for a TypePad Connect account and oyu will get one, though then you will likely use your TypePad Connect account to leave blog comments rather than your OpenID. </li>
<li>A TypePad Connect profile &#8211; lifestream, avatar, etc. </li>
<li>A comment feed &#8211; where you can track comments on posts you&#8217;ve also commented on, replies o your comments, etc. Provided, of course, the blogs you commented on use TypePad Connect (? I think).
</ul>
<p>So what do I see as the issues? Primarily they all follow from the idea that using TypePad Connect means replacing your blogging platforms built-in comment handling.</p>
<p>This means that:</p>
<ul>
<li>Comment-related plugins, search (of comments), moderation, anti-spam, and other features of your own blogging platform are disabled. </li>
<li>Change your mind down the road, and decide you&#8217;d like to move to another platform? Can you get your comments back, or bring them with you? What if you move to a platform TypePad Connect doesn&#8217;t support?</li>
</ul>
<p>Am I being too hard on SixApart? After all, they&#8217;re providing OpenIDs for all TypePad Connect profiles, enabling people to comment via OpenID. The profiles are also marked up with &#8220;rel=me&#8221; microformats, enabling the social graph style APIs to read them semantically. </p>
<p>Ultimately my concern isn&#8217;t with the TypePad Connect profile itself &#8211; if you don&#8217;t already have an existing lifestream and OpenID provider (Chi.mp, for example, or self-hosted like johneckman.com) it seems like a nice way to get one &#8211; but with the notion of replacing your blog&#8217;s comment moderation and management engine with an outsourced offering. </p>
<p>It seems too much like a shift towards a kind of walled-garden (to be fair, though, the content is open and available to all) of blog comments, in which users without TypePad Connect Profiles get a secondary experience. </p>
<p>It feels like a step backwards to ask users to create an account (albeit one which can be used on other sites too) just to be able to comment &#8211; but then nothing prevents users who have an existing OpenID, and a profile at that OpenID url, from using their existing &#8220;bring your own&#8221; style profile. </p>
<p>What do you think? Is TypePad Connect yet another step toward the open social web, or a step backwards in terms of openness? </p>
<p>For more on TypePad Connect, see the <a href="http://www.readwriteweb.com/archives/sixapart_typepad_connect.php">ReadWrite Web review</a>, or the <a href="http://www.typepad.com/connect/">TypePad Connect page</a> at SixApart. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.openparenthesis.org/2008/12/02/type-pad-disconnect-all-ur-comments-are-belong-to-us/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
	<enclosure url="http://www.openparenthesis.org/wp-content/uploads/2008/12/typepad_connect.png" length="145081" type="image/png" /><media:content url="http://www.openparenthesis.org/wp-content/uploads/2008/12/typepad_connect.png" width="502" height="354" medium="image" type="image/png" />	</item>
		<item>
		<title>Code Monkey Go To Job</title>
		<link>http://www.openparenthesis.org/2008/11/01/code-monkey-go-to-job</link>
		<comments>http://www.openparenthesis.org/2008/11/01/code-monkey-go-to-job#comments</comments>
		<pubDate>Sat, 01 Nov 2008 19:11:24 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[Friendster]]></category>
		<category><![CDATA[HorsePigCow]]></category>
		<category><![CDATA[Interview]]></category>
		<category><![CDATA[Jonathan Coulton]]></category>
		<category><![CDATA[Music]]></category>
		<category><![CDATA[MySpace]]></category>
		<category><![CDATA[Ownership]]></category>
		<category><![CDATA[Podcast]]></category>
		<category><![CDATA[social media]]></category>
		<category><![CDATA[Tara Hunt]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[YouTube]]></category>

		<guid isPermaLink="false">http://www.openparenthesis.org/?p=766</guid>
		<description><![CDATA[This summer Tara Hunt of HorsePigCow interviewed Jonathan Coulton. As a fan of both, I downloaded the podcast for later listening and then forgot all about. Finally got around to that &#8220;to listen to later&#8221; folder this morning, and would encourage you to check it out. If you&#8217;re not familiar with Coulton, two quick gems. [...]]]></description>
			<content:encoded><![CDATA[<p>This summer Tara Hunt of <a href="http://www.horsepigcow.com/2008/06/19/podcast-interview-jonathan-coulton/">HorsePigCow interviewed</a> <a href="http://www.jonathancoulton.com/">Jonathan Coulton</a>. As a fan of both, I downloaded the podcast for later listening and then forgot all about. Finally got around to that &#8220;to listen to later&#8221; folder this morning, and would encourage you to <a href="http://www.horsepigcow.com/2008/06/19/podcast-interview-jonathan-coulton/">check it out</a>. </p>
<p>If you&#8217;re not familiar with Coulton, two quick gems. First, <a href="http://www.jonathancoulton.com/2006/04/14/thing-a-week-29-code-monkey/">Code Monkey</a>:</p>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/j4TnhemCEmc&#038;hl=en&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/j4TnhemCEmc&#038;hl=en&#038;fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object></p>
<p>Second, his great cover of Sir Mix-a-Lot&#8217;s <a href="http://www.jonathancoulton.com/2005/10/14/thing-a-week-5-baby-got-back/">Baby Got Back</a>:</p>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/Ltjbnyvq_SI&#038;hl=en&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/Ltjbnyvq_SI&#038;hl=en&#038;fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object></p>
<p>In the interview (<a href="http://docs.google.com/View?docid=ah8ph6grxnqx_141g2wdxxdt">transcript here</a> if you prefer reading to listening &#8211; I&#8217;m quoting from the transcript), Coulton talks about his use of social media to create direct relationships with his audience, and why some approaches have been more effective than others:</p>
<blockquote><p>
Facebook and Myspace are essentially duplications of my blog and my email which I already have a blog and email so you know, I donâ€™t, I sort of donâ€™t understand why bands use something like Myspace unless the answer is they canâ€™t, they donâ€™t know how to make their own website</p></blockquote>
<p>Guess it helped that Coulton was originally a software developer. More to the point, Coulton identifies the risk of closed social networks and cloud platforms:</p>
<blockquote><p>I was always suspicious of Myspace because for the very simple reason that you donâ€™t have direct access to your network, you only have it through Myspace. If Myspace ever goes away your network winks out of existence, you donâ€™t have your emails you donâ€™t have any way of getting in touch with them. You are completely dependent on Myspace.</p>
<p>And you know you look at what happened with Friendster you know, guess what social networks rise and fall pretty quickly. That what happened with Friendster and itâ€™s sort of whatâ€™s happening with Myspace I guess and no matter how great and eternal you think a social network platform is itâ€™s an illusion itâ€™s going to go away. And so to spend all your time building up this Myspace network is I think has the potential to turn out not so well.</p></blockquote>
<p>Well put. I also really liked his point about creative commons licensing, which he leveraged very effectively early in his (recent) career and continues to use:</p>
<blockquote><p>. . . you know it was kind of a scary thing but I really just rationalised the thing, well letâ€™s just get the attention now and worry about making the money later, and you know, if the worst thing that happens is a million people get one of my songs for free, like you know, thatâ€™s okay, that something I can build on. And I would rather have that happen than make $15 from my friends who buy it and nobody else can hear it, you know. </p></blockquote>
<p>The interview also touches on Eventful, rickrolling, Wil Wheaton, Ze Frank, podcasting in general, YouTube, and (of course) Twitter. </p>
<p>Well worth a listen, especially but not exclusively if you&#8217;re and independent musician or wanna-be independent musician. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.openparenthesis.org/2008/11/01/code-monkey-go-to-job/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

