<?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: The future of corrections</title>
	<atom:link href="http://www.newsless.org/2009/03/the-future-of-corrections/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newsless.org/2009/03/the-future-of-corrections/</link>
	<description>Time to stop breaking the news, and start fixing it.*</description>
	<lastBuildDate>Sat, 13 Mar 2010 19:20:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: links for 2009-03-09 &#171; Synergias</title>
		<link>http://www.newsless.org/2009/03/the-future-of-corrections/comment-page-1/#comment-661</link>
		<dc:creator>links for 2009-03-09 &#171; Synergias</dc:creator>
		<pubDate>Mon, 09 Mar 2009 20:04:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.newsless.org/?p=369#comment-661</guid>
		<description>[...] The future of corrections at Newsless.org (tags: repórter21) [...]</description>
		<content:encoded><![CDATA[<p>[...] The future of corrections at Newsless.org (tags: repórter21) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David L.</title>
		<link>http://www.newsless.org/2009/03/the-future-of-corrections/comment-page-1/#comment-659</link>
		<dc:creator>David L.</dc:creator>
		<pubDate>Mon, 09 Mar 2009 07:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.newsless.org/?p=369#comment-659</guid>
		<description>Matt, 
 
 
 
As new methods to track errors develop, under what circumstances, if any, do you think journalists should be allowed to comment on corrections? 
 
 
Journalists do this already, but it&#039;s vague: &quot;Due to an editing error...&quot; Errors hurt credibility, but, at least in my experience, not all errors are malicious or even the product of stupidity. Part of me would love to be able to say, &quot;the CMS choked when we tried to save,&quot; or &quot;we&#039;re shortstaffed today,&quot; or &quot;there was miscommunication between the reporter and editor,&quot; or whatever. 
 We fix problems as soon as we see them. We try to improve.  
 
 
My initial concerns: First, this may be looking for love in all the wrong places. Nobody may care whether we&#039;re blameworthy for a mistake. Publicizing will still, fairly or unfairly, hurt our credibility over time. 
 
Second, journalists would need an incentive to actually explain errors more than &quot;due to an editing error...,&quot; and &lt;a href=&quot;http://en.wikipedia.org/wiki/Cognitive_dissonance&quot; target=&quot;_blank&quot;&gt;who wants to admit a mistake?&lt;/a&gt; 
 
 
Perhaps, though, news organizations&#039; credibility should be punished for errors no matter whether the error was malicious. I would be open to that argument as well. </description>
		<content:encoded><![CDATA[<p>Matt, </p>
<p>As new methods to track errors develop, under what circumstances, if any, do you think journalists should be allowed to comment on corrections? </p>
<p>Journalists do this already, but it&#039;s vague: &quot;Due to an editing error&#8230;&quot; Errors hurt credibility, but, at least in my experience, not all errors are malicious or even the product of stupidity. Part of me would love to be able to say, &quot;the CMS choked when we tried to save,&quot; or &quot;we&#039;re shortstaffed today,&quot; or &quot;there was miscommunication between the reporter and editor,&quot; or whatever.<br />
 We fix problems as soon as we see them. We try to improve.  </p>
<p>My initial concerns: First, this may be looking for love in all the wrong places. Nobody may care whether we&#039;re blameworthy for a mistake. Publicizing will still, fairly or unfairly, hurt our credibility over time. </p>
<p>Second, journalists would need an incentive to actually explain errors more than &quot;due to an editing error&#8230;,&quot; and <a href="http://en.wikipedia.org/wiki/Cognitive_dissonance" target="_blank">who wants to admit a mistake?</a> </p>
<p>Perhaps, though, news organizations&#039; credibility should be punished for errors no matter whether the error was malicious. I would be open to that argument as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris_Amico</title>
		<link>http://www.newsless.org/2009/03/the-future-of-corrections/comment-page-1/#comment-658</link>
		<dc:creator>Chris_Amico</dc:creator>
		<pubDate>Sat, 07 Mar 2009 22:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.newsless.org/?p=369#comment-658</guid>
		<description>&lt;a href=&quot;http://www.palewire.com&quot; target=&quot;_blank&quot;&gt;Ben Welsh&lt;/a&gt; at the LA Times started an interesting corrections application a little while ago that seems to fit with this post: &lt;a href=&quot;http://github.com/palewire/django-correx/tree/master&quot; target=&quot;_blank&quot;&gt;http://github.com/palewire/django-correx/tree/mas...&lt;/a&gt; 
 
It wouldn&#039;t be hard, I think, to build in a way to attach corrections to stories, blog posts, etc, and publish a stream of those, linking back to the original work and making it easy for readers to find what&#039;s been changed. Part of it is cultural, as you said, but the tech side shouldn&#039;t be too hard. </description>
		<content:encoded><![CDATA[<p><a href="http://www.palewire.com" target="_blank">Ben Welsh</a> at the LA Times started an interesting corrections application a little while ago that seems to fit with this post: <a href="http://github.com/palewire/django-correx/tree/master" target="_blank"></a><a href="http://github.com/palewire/django-correx/tree/mas.." rel="nofollow">http://github.com/palewire/django-correx/tree/mas..</a>. </p>
<p>It wouldn&#039;t be hard, I think, to build in a way to attach corrections to stories, blog posts, etc, and publish a stream of those, linking back to the original work and making it easy for readers to find what&#039;s been changed. Part of it is cultural, as you said, but the tech side shouldn&#039;t be too hard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig_Silverman</title>
		<link>http://www.newsless.org/2009/03/the-future-of-corrections/comment-page-1/#comment-652</link>
		<dc:creator>Craig_Silverman</dc:creator>
		<pubDate>Fri, 06 Mar 2009 01:15:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.newsless.org/?p=369#comment-652</guid>
		<description>Great post, Matt. Your call for a corrections notification system for readers is really on point. I&#039;ve been trying to generate some interest in the idea of a &quot;reverse trackback&quot; that could also provide an automated way to notify blogs and other sites if an article they quoted has been corrected/updated. I wrote about it here: 
&lt;a href=&quot;http://www.regrettheerror.com/regret-articles/corrections-and-accuracy-wishes-for-the-new-year&quot; target=&quot;_blank&quot;&gt;http://www.regrettheerror.com/regret-articles/cor...&lt;/a&gt; 
 
Also, you should check out the way Slate handles corrections; they have a very cool system that shows readers exactly where the mistake occurred in a given article. </description>
		<content:encoded><![CDATA[<p>Great post, Matt. Your call for a corrections notification system for readers is really on point. I&#039;ve been trying to generate some interest in the idea of a &quot;reverse trackback&quot; that could also provide an automated way to notify blogs and other sites if an article they quoted has been corrected/updated. I wrote about it here:<br />
<a href="http://www.regrettheerror.com/regret-articles/corrections-and-accuracy-wishes-for-the-new-year" target="_blank"></a><a href="http://www.regrettheerror.com/regret-articles/cor.." rel="nofollow">http://www.regrettheerror.com/regret-articles/cor..</a>. </p>
<p>Also, you should check out the way Slate handles corrections; they have a very cool system that shows readers exactly where the mistake occurred in a given article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ricky</title>
		<link>http://www.newsless.org/2009/03/the-future-of-corrections/comment-page-1/#comment-651</link>
		<dc:creator>ricky</dc:creator>
		<pubDate>Thu, 05 Mar 2009 06:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.newsless.org/?p=369#comment-651</guid>
		<description>I think your wiki idea is a good one, as is a crowd-sourced corrections site... It would help police after-the-fact changes from the new media and old media alike... things are not as pure as you portray in the new media... here are two documented instances where they made changes without noting them. &lt;a href=&quot;http://tinyurl.com/ex-facto-post&quot; target=&quot;_blank&quot;&gt;http://tinyurl.com/ex-facto-post&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>I think your wiki idea is a good one, as is a crowd-sourced corrections site&#8230; It would help police after-the-fact changes from the new media and old media alike&#8230; things are not as pure as you portray in the new media&#8230; here are two documented instances where they made changes without noting them. <a href="http://tinyurl.com/ex-facto-post" target="_blank">http://tinyurl.com/ex-facto-post</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
