<?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: Google Reader vs. Bloglines</title>
	<atom:link href="http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/feed/" rel="self" type="application/rss+xml" />
	<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/</link>
	<description>Making next year's Human-Computer family reunion a lot less uncomfortable.</description>
	<lastBuildDate>Tue, 02 Feb 2010 20:14:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bloglines (beta) vs. Google Reader (!beta?) &#124; Matthew Oliphant&#8217;s usabilityworks.org</title>
		<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/comment-page-1/#comment-51416</link>
		<dc:creator>Bloglines (beta) vs. Google Reader (!beta?) &#124; Matthew Oliphant&#8217;s usabilityworks.org</dc:creator>
		<pubDate>Tue, 05 Feb 2008 20:32:17 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/#comment-51416</guid>
		<description>[...] since I have my own blog I really should be commenting here. 3) It&#8217;s been over a year since I compared Bloglines and Google Reader and it&#8217;s likely time for an [...]</description>
		<content:encoded><![CDATA[<p>[...] since I have my own blog I really should be commenting here. 3) It&#8217;s been over a year since I compared Bloglines and Google Reader and it&#8217;s likely time for an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How I Wish RSS Subscribing Would Work &#124; Matthew Oliphant&#8217;s usabilityworks.org</title>
		<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/comment-page-1/#comment-51156</link>
		<dc:creator>How I Wish RSS Subscribing Would Work &#124; Matthew Oliphant&#8217;s usabilityworks.org</dc:creator>
		<pubDate>Thu, 01 Nov 2007 14:57:17 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/#comment-51156</guid>
		<description>[...] I click on the Subscribe button, I am taken to Bloglines (my reader of choice) to finish the subscription [...]</description>
		<content:encoded><![CDATA[<p>[...] I click on the Subscribe button, I am taken to Bloglines (my reader of choice) to finish the subscription [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/comment-page-1/#comment-4681</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Thu, 23 Nov 2006 14:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/#comment-4681</guid>
		<description>Mike, that preference wasn&#039;t available when I did the above review.  It just seems ass-backwards that when I &quot;open&quot; an item it isn&#039;t marked read.  

Given how most content applications work, I would have suspected to be able to set a preference to get Google Reader&#039;s default way of marking items read, not the other way around.

In the end, I believe the choice between the two (or the choice of how to read content) becomes a matter of preference.  I suppose I am too ingrained in Bloglines to make the jump to another way of reading that, while similar, is different enough to cause me some cognitive dissonance.</description>
		<content:encoded><![CDATA[<p>Mike, that preference wasn&#8217;t available when I did the above review.  It just seems ass-backwards that when I &#8220;open&#8221; an item it isn&#8217;t marked read.  </p>
<p>Given how most content applications work, I would have suspected to be able to set a preference to get Google Reader&#8217;s default way of marking items read, not the other way around.</p>
<p>In the end, I believe the choice between the two (or the choice of how to read content) becomes a matter of preference.  I suppose I am too ingrained in Bloglines to make the jump to another way of reading that, while similar, is different enough to cause me some cognitive dissonance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/comment-page-1/#comment-4677</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 23 Nov 2006 07:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/#comment-4677</guid>
		<description>&lt;blockquote&gt;Making me click to tell you I read something just slows me down. The Bloglines model is better. Loading content is marking it read.&lt;/blockquote&gt;

Its an option in the Google reader.  Set it and forget it.  I agree that I would never want to click on an item to mark it &quot;read&quot;.  Read is read.  But don&#039;t blame Google &#039;cos you didn&#039;t set the options to match your preferences.

After using Bloglines for a long, &lt;em&gt;long&lt;/em&gt; time, then Google Reader for a few days (it quickly got irritating,) &lt;a href=&quot;http://mikro2nd.net/blog/mike/the+web/2006/11/15/Feedburners-Flame-Flickers.html&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;I have finally settled on Flock&lt;/a&gt; (http://flock.com/).  Not an online reader, and it has a few quirks of its own, but I am still finding it a &lt;em&gt;very&lt;/em&gt; fast way to track a lot of feeds, not to mention great for gathering bloggable info and as a blog editor.  And, No, I have no connection with the Flock project other than as a pretty happy beta user ;-)</description>
		<content:encoded><![CDATA[<blockquote><p>Making me click to tell you I read something just slows me down. The Bloglines model is better. Loading content is marking it read.</p></blockquote>
<p>Its an option in the Google reader.  Set it and forget it.  I agree that I would never want to click on an item to mark it &#8220;read&#8221;.  Read is read.  But don&#8217;t blame Google &#8216;cos you didn&#8217;t set the options to match your preferences.</p>
<p>After using Bloglines for a long, <em>long</em> time, then Google Reader for a few days (it quickly got irritating,) <a href="http://mikro2nd.net/blog/mike/the+web/2006/11/15/Feedburners-Flame-Flickers.html" rel="nofollow" rel="nofollow" rel="nofollow">I have finally settled on Flock</a> (<a href="http://flock.com/" rel="nofollow">http://flock.com/</a>).  Not an online reader, and it has a few quirks of its own, but I am still finding it a <em>very</em> fast way to track a lot of feeds, not to mention great for gathering bloggable info and as a blog editor.  And, No, I have no connection with the Flock project other than as a pretty happy beta user ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/comment-page-1/#comment-1506</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Wed, 11 Oct 2006 17:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/#comment-1506</guid>
		<description>Yep, I was late to the party.  I am still using both apps.  As I go through the day I try to use one first, then the other, then flip that the next time.

I still really do not like the disappearing content in the Google Reader.  Just because I click on it doesn&#039;t mean I am done reading.</description>
		<content:encoded><![CDATA[<p>Yep, I was late to the party.  I am still using both apps.  As I go through the day I try to use one first, then the other, then flip that the next time.</p>
<p>I still really do not like the disappearing content in the Google Reader.  Just because I click on it doesn&#8217;t mean I am done reading.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C</title>
		<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/comment-page-1/#comment-1504</link>
		<dc:creator>C</dc:creator>
		<pubDate>Wed, 11 Oct 2006 14:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/#comment-1504</guid>
		<description>Another &lt;a href=&quot;http://www.iqcontent.com/blog/2006/10/battle-of-the-rss-readers-bloglines-versus-google-reader&quot; rel=&quot;nofollow&quot;&gt;review&lt;/a&gt; made a few days before yours.
</description>
		<content:encoded><![CDATA[<p>Another <a href="http://www.iqcontent.com/blog/2006/10/battle-of-the-rss-readers-bloglines-versus-google-reader" rel="nofollow">review</a> made a few days before yours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/comment-page-1/#comment-1485</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Tue, 10 Oct 2006 15:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2006/10/10/google-reader-vs-bloglines/#comment-1485</guid>
		<description>An yes, I do know that I am complaining about software I get to use for free. :)</description>
		<content:encoded><![CDATA[<p>An yes, I do know that I am complaining about software I get to use for free. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
