<?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: &#039;Think before you act&#039; and more rules for journalists on Twitter</title>
	<atom:link href="http://www.ojr.org/think-before-you-act-and-more-rules-for-journalists-on-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ojr.org/think-before-you-act-and-more-rules-for-journalists-on-twitter/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=think-before-you-act-and-more-rules-for-journalists-on-twitter</link>
	<description>Focusing on the future of digital journalism</description>
	<lastBuildDate>Mon, 15 Apr 2013 13:43:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Steve Fox</title>
		<link>http://www.ojr.org/think-before-you-act-and-more-rules-for-journalists-on-twitter/#comment-2795</link>
		<dc:creator>Steve Fox</dc:creator>
		<pubDate>Sat, 04 Feb 2012 12:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=2051#comment-2795</guid>
		<description><![CDATA[Hi Andy --

Thanks for your comment.  The piece was not meant as an attack on you or NPR but unfortunately the Giffords case is an example of a profession that sometimes moves to fast.

As for the specifics that you outline here, I think that, yes, the need to slow down and fact-check is necessary, especially when it comes to breaking news. You do this now on Twitter when you ask the crowd for confirmation.

In this case, I think both the Web editor and the person tweeting (you) needed to fact-check -- I know of other news organizations where the Web platform will do its own reporting against what their broadcast platform is reporting.

Is it practical?  Well, I think the value of being &quot;first&quot; today is overblown when we measure all the stumbles we&#039;ve seen.  I like ESPN&#039;s idea of not breaking news on Twitter....it creates a slowing down process.

chrs,
Steve


]]></description>
		<content:encoded><![CDATA[<p>Hi Andy &#8211;</p>
<p>Thanks for your comment.  The piece was not meant as an attack on you or NPR but unfortunately the Giffords case is an example of a profession that sometimes moves to fast.</p>
<p>As for the specifics that you outline here, I think that, yes, the need to slow down and fact-check is necessary, especially when it comes to breaking news. You do this now on Twitter when you ask the crowd for confirmation.</p>
<p>In this case, I think both the Web editor and the person tweeting (you) needed to fact-check &#8212; I know of other news organizations where the Web platform will do its own reporting against what their broadcast platform is reporting.</p>
<p>Is it practical?  Well, I think the value of being &#8220;first&#8221; today is overblown when we measure all the stumbles we&#8217;ve seen.  I like ESPN&#8217;s idea of not breaking news on Twitter&#8230;.it creates a slowing down process.</p>
<p>chrs,<br />
Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 74.82.64.35</title>
		<link>http://www.ojr.org/think-before-you-act-and-more-rules-for-journalists-on-twitter/#comment-2794</link>
		<dc:creator>74.82.64.35</dc:creator>
		<pubDate>Fri, 27 Jan 2012 14:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=2051#comment-2794</guid>
		<description><![CDATA[Great post, steve. As a journalist who&#039;d rather be tardy and accurate than early and erroneous, I couldn&#039;t agree more! ]]></description>
		<content:encoded><![CDATA[<p>Great post, steve. As a journalist who&#8217;d rather be tardy and accurate than early and erroneous, I couldn&#8217;t agree more! </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 205.153.36.170</title>
		<link>http://www.ojr.org/think-before-you-act-and-more-rules-for-journalists-on-twitter/#comment-2793</link>
		<dc:creator>205.153.36.170</dc:creator>
		<pubDate>Fri, 27 Jan 2012 14:15:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=2051#comment-2793</guid>
		<description><![CDATA[Hi Steve,

Andy Carvin here. Bringing up the NPR example is always an important one - I should know, as I was the one who wrote that tweet. The one thing I&#039;m still trying to figure out is what practices could have been in place to have prevented me from sending the tweet.

The problem is that this was first and foremost a reporting mistake. The editor running the news desk that day decided to report her &quot;death&quot; on our hourly radio newscast. The weekend Web editors were then alerted to this, and they posted it as the lead story on our homepage, then sent out an email alert to our breaking news subscribers. That&#039;s actually how I found out about it - I was at a restaurant with my family and got the breaking news alert from NPR. It was at that point that I noticed that no one was updating NPR&#039;s Twitter account - its most recent post was reporting Giffords was alive - so I took the headline as represented on our homepage and in the breaking news alert.

So does that leave me partially at fault? In the sense that I was part of the cascade of failures that day, yes. But it was indeed a cascade - something that was reported first on radio, then the Web, then email, and then twitter. But does that make it primarily a twitter mistake that could have been avoided in the way you outlined in your post?

The following day, I wrote on a blog discussing the mistake that I felt I needed to report it on twitter, since we had already done so on our other platforms; second-guessing our editors and asking them for more proof is the job of our other editors. But is it my job too? Is it realistic for staff who maintain a news org&#039;s presence on additional platforms and aren&#039;t part of the editorial change to challenge the reporting that&#039;s already been edited and appeared on our primary platforms? Practically speaking, it&#039;s impossible to do it routinely, or everything would grind to a halt. But should there exceptions?

Looking forward to hearing your thoughts. - Andy

Thanks,
andy]]></description>
		<content:encoded><![CDATA[<p>Hi Steve,</p>
<p>Andy Carvin here. Bringing up the NPR example is always an important one &#8211; I should know, as I was the one who wrote that tweet. The one thing I&#8217;m still trying to figure out is what practices could have been in place to have prevented me from sending the tweet.</p>
<p>The problem is that this was first and foremost a reporting mistake. The editor running the news desk that day decided to report her &#8220;death&#8221; on our hourly radio newscast. The weekend Web editors were then alerted to this, and they posted it as the lead story on our homepage, then sent out an email alert to our breaking news subscribers. That&#8217;s actually how I found out about it &#8211; I was at a restaurant with my family and got the breaking news alert from NPR. It was at that point that I noticed that no one was updating NPR&#8217;s Twitter account &#8211; its most recent post was reporting Giffords was alive &#8211; so I took the headline as represented on our homepage and in the breaking news alert.</p>
<p>So does that leave me partially at fault? In the sense that I was part of the cascade of failures that day, yes. But it was indeed a cascade &#8211; something that was reported first on radio, then the Web, then email, and then twitter. But does that make it primarily a twitter mistake that could have been avoided in the way you outlined in your post?</p>
<p>The following day, I wrote on a blog discussing the mistake that I felt I needed to report it on twitter, since we had already done so on our other platforms; second-guessing our editors and asking them for more proof is the job of our other editors. But is it my job too? Is it realistic for staff who maintain a news org&#8217;s presence on additional platforms and aren&#8217;t part of the editorial change to challenge the reporting that&#8217;s already been edited and appeared on our primary platforms? Practically speaking, it&#8217;s impossible to do it routinely, or everything would grind to a halt. But should there exceptions?</p>
<p>Looking forward to hearing your thoughts. &#8211; Andy</p>
<p>Thanks,<br />
andy</p>
]]></content:encoded>
	</item>
</channel>
</rss>