<?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: Authenticated Commenting Needs Help</title>
	<atom:link href="http://blog.fav.or.it/2008/08/authenticated-commenting-needs-help/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fav.or.it/2008/08/authenticated-commenting-needs-help/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 09 Aug 2009 21:55:33 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nick Halstead</title>
		<link>http://blog.fav.or.it/2008/08/authenticated-commenting-needs-help/comment-page-1/#comment-998</link>
		<dc:creator>Nick Halstead</dc:creator>
		<pubDate>Thu, 28 Aug 2008 12:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fav.or.it/?p=142#comment-998</guid>
		<description>Hi Mike,

I was being general on the Feed side, as ATOM/RSS are so abused anyway that just because a specification says it includes something does not mean anyone conforms to it. But for us the URL was never a good means to identify the commentor purely because it can be abused, so we are very black and white on this, either its anonymous or its properly authenticated.

For the mass market (the only thing we care about) url&#039;s are a no go anyway (as stated in the post) - but as more platforms are making their identity available through API&#039;s (e.g. Facebook + Myspace) I see a good future for comenting.</description>
		<content:encoded><![CDATA[<p>Hi Mike,</p>
<p>I was being general on the Feed side, as ATOM/RSS are so abused anyway that just because a specification says it includes something does not mean anyone conforms to it. But for us the URL was never a good means to identify the commentor purely because it can be abused, so we are very black and white on this, either its anonymous or its properly authenticated.</p>
<p>For the mass market (the only thing we care about) url&#8217;s are a no go anyway (as stated in the post) &#8211; but as more platforms are making their identity available through API&#8217;s (e.g. Facebook + Myspace) I see a good future for comenting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Montano</title>
		<link>http://blog.fav.or.it/2008/08/authenticated-commenting-needs-help/comment-page-1/#comment-997</link>
		<dc:creator>Mike Montano</dc:creator>
		<pubDate>Thu, 28 Aug 2008 12:17:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fav.or.it/?p=142#comment-997</guid>
		<description>Hey Nick,

We absolutely agree that authenticated commenting is a good thing. A few things of note, BackType does very little scraping. ATOM feeds _do_ contain urls and we do make use of APIs that allow to ensure authenticated comments.

This is still something we are working on and is one of the reasons why we like systems like Disqus and IntenseDebate.</description>
		<content:encoded><![CDATA[<p>Hey Nick,</p>
<p>We absolutely agree that authenticated commenting is a good thing. A few things of note, BackType does very little scraping. ATOM feeds _do_ contain urls and we do make use of APIs that allow to ensure authenticated comments.</p>
<p>This is still something we are working on and is one of the reasons why we like systems like Disqus and IntenseDebate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
