<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Twitter hints for reporters</title>
	<atom:link href="http://ryansholin.com/2007/12/13/twitter-hints-for-reporters/feed/" rel="self" type="application/rss+xml" />
	<link>http://ryansholin.com/2007/12/13/twitter-hints-for-reporters/</link>
	<description>Ryan Sholin on the future of newspapers, online news and journalism education.</description>
	<lastBuildDate>Thu, 11 Mar 2010 02:29:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: thejjunkie.com &#187; Blog Archive &#187; A bit of link-blogging in the morning</title>
		<link>http://ryansholin.com/2007/12/13/twitter-hints-for-reporters/comment-page-1/#comment-9533</link>
		<dc:creator>thejjunkie.com &#187; Blog Archive &#187; A bit of link-blogging in the morning</dc:creator>
		<pubDate>Fri, 21 Dec 2007 11:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryansholin.com/2007/12/13/twitter-hints-for-reporters/#comment-9533</guid>
		<description>[...] 75% in; I have to admit I haven&#8217;t bothered with de.li.cio.us yet. Ryan also instructs you about Twitter; I created an account weeks ago, and that&#8217;s as far as I&#8217;ve gone. Now Ryan is going to [...]</description>
		<content:encoded><![CDATA[<p>[...] 75% in; I have to admit I haven&#8217;t bothered with de.li.cio.us yet. Ryan also instructs you about Twitter; I created an account weeks ago, and that&#8217;s as far as I&#8217;ve gone. Now Ryan is going to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: knackeredhack</title>
		<link>http://ryansholin.com/2007/12/13/twitter-hints-for-reporters/comment-page-1/#comment-9472</link>
		<dc:creator>knackeredhack</dc:creator>
		<pubDate>Fri, 14 Dec 2007 11:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryansholin.com/2007/12/13/twitter-hints-for-reporters/#comment-9472</guid>
		<description>Ryan, this is very insightful.  

I&#039;ve done this kind of intelligence gathering a long time ago in the financial newsagency arena, using mIRC as the mechanism, but within the firewall.  It was highly unusual then, and I suspect still so now, because journalists don&#039;t seem so good at sharing.  The subjects for interview would be central banking types.  Reporters  in the global network would be tapped for input, offering different technical or market perspectives.  This could even be done with doorstep interviews to produce realtime feedback between subject and audience. The interviewer could look way smarter this way too, so you build credibility with who you are talking to.

The problem with working on your own is what is known as the availability error/heuristic.  Tapping a wider faculty could unfortunately reinforce that, unless you maintain diversity in your network.  Of course if your editor suffers from availability error, you&#039;re screwed.

Better go off and twitter now.</description>
		<content:encoded><![CDATA[<p>Ryan, this is very insightful.  </p>
<p>I&#8217;ve done this kind of intelligence gathering a long time ago in the financial newsagency arena, using mIRC as the mechanism, but within the firewall.  It was highly unusual then, and I suspect still so now, because journalists don&#8217;t seem so good at sharing.  The subjects for interview would be central banking types.  Reporters  in the global network would be tapped for input, offering different technical or market perspectives.  This could even be done with doorstep interviews to produce realtime feedback between subject and audience. The interviewer could look way smarter this way too, so you build credibility with who you are talking to.</p>
<p>The problem with working on your own is what is known as the availability error/heuristic.  Tapping a wider faculty could unfortunately reinforce that, unless you maintain diversity in your network.  Of course if your editor suffers from availability error, you&#8217;re screwed.</p>
<p>Better go off and twitter now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
