<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Beware of silent corrections&#8230;</title>
	<atom:link href="http://www.thetlog.net/2006/03/24/beware-of-silent-corrections/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thetlog.net/2006/03/24/beware-of-silent-corrections/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 07:55:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Eric Lunt</title>
		<link>http://www.thetlog.net/2006/03/24/beware-of-silent-corrections/#comment-1015</link>
		<dc:creator>Eric Lunt</dc:creator>
		<pubDate>Mon, 27 Mar 2006 17:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.thetlog.net/2006/03/24/beware-of-silent-corrections/#comment-1015</guid>
		<description>Hello there. I&#039;d actually be surprised if we were able to fix that ... if we get an XML error in the source feed, what we&#039;ll usually do is 1) write an entry to the publisher&#039;s FeedBulletin to let them know there&#039;s a problem (see your &quot;My Account&quot; page for more info on that), and 2) return the &quot;last-known-good&quot; version of the feed. Maybe #2 is what you&#039;re referring to? But then it would have looked like your feeds were frozen and not updating for weeks.

Anyway, thanks for posting, and we&#039;ll be sure to watch for this situation.

Eric Lunt
CTO, FeedBurner</description>
		<content:encoded><![CDATA[<p>Hello there. I&#8217;d actually be surprised if we were able to fix that &#8230; if we get an XML error in the source feed, what we&#8217;ll usually do is 1) write an entry to the publisher&#8217;s FeedBulletin to let them know there&#8217;s a problem (see your &#8220;My Account&#8221; page for more info on that), and 2) return the &#8220;last-known-good&#8221; version of the feed. Maybe #2 is what you&#8217;re referring to? But then it would have looked like your feeds were frozen and not updating for weeks.</p>
<p>Anyway, thanks for posting, and we&#8217;ll be sure to watch for this situation.</p>
<p>Eric Lunt<br />
CTO, FeedBurner</p>
]]></content:encoded>
	</item>
</channel>
</rss>

