<?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: RSS Readers Hinder Discussion</title>
	<atom:link href="http://chadlehman.com/?feed=rss2&#038;p=316" rel="self" type="application/rss+xml" />
	<link>http://chadlehman.com/?p=316</link>
	<description>Teaching, Technology, the Library, &#38; more.</description>
	<lastBuildDate>Sat, 28 Aug 2010 03:19:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Robinson</title>
		<link>http://chadlehman.com/?p=316&#038;cpage=1#comment-2645</link>
		<dc:creator>John Robinson</dc:creator>
		<pubDate>Tue, 24 Nov 2009 15:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://chadlehman.com/?p=316#comment-2645</guid>
		<description>Hi Chad,

Connecting the conversation is a very relevant topic for what we&#039;re doing at Joyspoon so thanks for your thoughts on the issue! 

I think there are two main problems with RSS and the conversation right now. The main issue is one which I feel most people don&#039;t give enough weight to, and that is the low adoption rate of RSS amongst the non-techy crowd. This makes it hard for non-RSS readers to not only stay up to date on the latest content but also to sustain any sort of meaningful conversation. By making it difficult for the average web user to stay up to date on your content, you reduce the total number of users participating in the discussion right from the beginning.

For the users who are RSS readers, the main issue I&#039;ve found is exactly what you&#039;ve said above, the lack of an integrated community component. 

I seem to get into a groove when I read RSS feeds and unless the article really speaks to me, I will very rarely click-through. And when I do, I feel the need to write long-winded comments like this. If there was a way to package the discussion with the content, I think it&#039;d just become part of my routine and I&#039;d become a more active participant on a larger number of blogs.

(Teaser: we&#039;ve found solutions for both of the above problems, send me off an email if you want to see how we&#039;re doing it!)

Anyways, always a great topic! Looking forward to hearing what others think.

John Robinson
Joyspoon Community Manager
Twitter: @Joyspoon</description>
		<content:encoded><![CDATA[<p>Hi Chad,</p>
<p>Connecting the conversation is a very relevant topic for what we&#8217;re doing at Joyspoon so thanks for your thoughts on the issue! </p>
<p>I think there are two main problems with RSS and the conversation right now. The main issue is one which I feel most people don&#8217;t give enough weight to, and that is the low adoption rate of RSS amongst the non-techy crowd. This makes it hard for non-RSS readers to not only stay up to date on the latest content but also to sustain any sort of meaningful conversation. By making it difficult for the average web user to stay up to date on your content, you reduce the total number of users participating in the discussion right from the beginning.</p>
<p>For the users who are RSS readers, the main issue I&#8217;ve found is exactly what you&#8217;ve said above, the lack of an integrated community component. </p>
<p>I seem to get into a groove when I read RSS feeds and unless the article really speaks to me, I will very rarely click-through. And when I do, I feel the need to write long-winded comments like this. If there was a way to package the discussion with the content, I think it&#8217;d just become part of my routine and I&#8217;d become a more active participant on a larger number of blogs.</p>
<p>(Teaser: we&#8217;ve found solutions for both of the above problems, send me off an email if you want to see how we&#8217;re doing it!)</p>
<p>Anyways, always a great topic! Looking forward to hearing what others think.</p>
<p>John Robinson<br />
Joyspoon Community Manager<br />
Twitter: @Joyspoon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cathy NElson</title>
		<link>http://chadlehman.com/?p=316&#038;cpage=1#comment-2644</link>
		<dc:creator>Cathy NElson</dc:creator>
		<pubDate>Tue, 24 Nov 2009 00:05:58 +0000</pubDate>
		<guid isPermaLink="false">http://chadlehman.com/?p=316#comment-2644</guid>
		<description>I use Google Reader too, but if a post strikes me as interesting, I open it in another tab to be looked at again later, and then possibly comment. (But of course this one I went directly too for my comment!)

I dont mind having to link out, as it 1) gives me a chance to see if there are already comments there so I can extend the conversation and 2)more time to reflect and sometimes calm down my emotional response.

My pet peeve is that many bloggers DON&#039;T offer a comments feed in their blog, making it impossible to follow the conversations. Some confess they don&#039;t know how.  I say to that, EZ, pick a new blog theme.  No excuse is accepted. Ive dropped some from my reader for that reason alone before. 

Once again, nice post.  I&#039;ve blogged about it before too.</description>
		<content:encoded><![CDATA[<p>I use Google Reader too, but if a post strikes me as interesting, I open it in another tab to be looked at again later, and then possibly comment. (But of course this one I went directly too for my comment!)</p>
<p>I dont mind having to link out, as it 1) gives me a chance to see if there are already comments there so I can extend the conversation and 2)more time to reflect and sometimes calm down my emotional response.</p>
<p>My pet peeve is that many bloggers DON&#8217;T offer a comments feed in their blog, making it impossible to follow the conversations. Some confess they don&#8217;t know how.  I say to that, EZ, pick a new blog theme.  No excuse is accepted. Ive dropped some from my reader for that reason alone before. </p>
<p>Once again, nice post.  I&#8217;ve blogged about it before too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
