
<?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: Feed Problem</title>
	<atom:link href="http://www.mayvelous.com/2009/01/31/feed-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mayvelous.com/2009/01/31/feed-problem/</link>
	<description>Me, Myself and Mayvelous</description>
	<lastBuildDate>Tue, 17 Jan 2012 06:37:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Gabe</title>
		<link>http://www.mayvelous.com/2009/01/31/feed-problem/comment-page-1/#comment-46876</link>
		<dc:creator>Gabe</dc:creator>
		<pubDate>Tue, 03 Feb 2009 01:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mayvelous.com/2009/01/31/feed-problem/#comment-46876</guid>
		<description>Your feed reader does not know how determine a unique post except by URL. 

Most readers would be smart enough to use the URL of the original article, but some also use the URL of the RSS feed for reference. 

It may also be the type of redirect your old feed has to the new one. If its a HTTP redirect, which is most likely it should be ok. Some HTTP Clients though will not follow more then 1 redirect. So if you have another HTTP redirect to the original source of the article, then your feed reader may not want to follow that far. 

eg: If you had an RSS feed on for Google News. Then syndicated that feed from feedburner. Then when an RSS client views the feed on feedburner it find each article redirects first to google news, then google redirects to the original news article, or even to another syndication of the news article. Some RSS clients will give up along the way and just list the first or second URL. 

Worst part is Google news randomly employs different redirect types, rotating between HTTP and Meta Refresh (HTML based redirect) - probably out of scope here.</description>
		<content:encoded><![CDATA[<p>Your feed reader does not know how determine a unique post except by URL. </p>
<p>Most readers would be smart enough to use the URL of the original article, but some also use the URL of the RSS feed for reference. </p>
<p>It may also be the type of redirect your old feed has to the new one. If its a HTTP redirect, which is most likely it should be ok. Some HTTP Clients though will not follow more then 1 redirect. So if you have another HTTP redirect to the original source of the article, then your feed reader may not want to follow that far. </p>
<p>eg: If you had an RSS feed on for Google News. Then syndicated that feed from feedburner. Then when an RSS client views the feed on feedburner it find each article redirects first to google news, then google redirects to the original news article, or even to another syndication of the news article. Some RSS clients will give up along the way and just list the first or second URL. </p>
<p>Worst part is Google news randomly employs different redirect types, rotating between HTTP and Meta Refresh (HTML based redirect) &#8211; probably out of scope here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

