<?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"
	>
<channel>
	<title>Comments on: Bloglines (beta) vs. Google Reader (!beta?)</title>
	<atom:link href="http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/feed/" rel="self" type="application/rss+xml" />
	<link>http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/</link>
	<description>Making next year's Human-Computer family reunion a lot less uncomfortable.</description>
	<pubDate>Mon, 06 Oct 2008 16:57:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/#comment-51426</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Thu, 07 Feb 2008 02:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/#comment-51426</guid>
		<description>I am trying out Google Reader again for the rest of the week.  One thing so far that I like Bloglines Beta better for is the J key when you are "in" a particular feed.

In Google Reader, J only gets you through the posts of that feed.  In Bloglines Beta, once you've reached the end of a feed's posts, it jumps to the next feed in your list and you can just keep going.  I like that a lot and wish Google Reader would do it.</description>
		<content:encoded><![CDATA[<p>I am trying out Google Reader again for the rest of the week.  One thing so far that I like Bloglines Beta better for is the J key when you are &#8220;in&#8221; a particular feed.</p>
<p>In Google Reader, J only gets you through the posts of that feed.  In Bloglines Beta, once you&#8217;ve reached the end of a feed&#8217;s posts, it jumps to the next feed in your list and you can just keep going.  I like that a lot and wish Google Reader would do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bloglines Beta vs Google Reader &#124; SuccessCREEations, Inc.</title>
		<link>http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/#comment-51421</link>
		<dc:creator>Bloglines Beta vs Google Reader &#124; SuccessCREEations, Inc.</dc:creator>
		<pubDate>Wed, 06 Feb 2008 01:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/#comment-51421</guid>
		<description>[...] whether her evaluation of the two stands up, check out Matthew Oliphant&#8217;s response post comparing the two. He comes up with the same [...]</description>
		<content:encoded><![CDATA[<p>[...] whether her evaluation of the two stands up, check out Matthew Oliphant&#8217;s response post comparing the two. He comes up with the same [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/#comment-51420</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Tue, 05 Feb 2008 21:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2008/02/05/bloglines-beta-vs-google-reader-beta/#comment-51420</guid>
		<description>Wow.  I am already #2 for &lt;a href="http://www.google.com/search?num=100&#038;hl=en&#038;safe=off&#038;client=firefox-a&#038;rls=org.mozilla:en-US:official&#038;q=google reader vs bloglines beta&#038;btnG=Search" rel="nofollow"&gt;bloglines beta vs. google reader&lt;/a&gt;.  At least, in my view of the search results.  I know position can vary depending on who is searching.</description>
		<content:encoded><![CDATA[<p>Wow.  I am already #2 for <a href="http://www.google.com/search?num=100&#038;hl=en&#038;safe=off&#038;client=firefox-a&#038;rls=org.mozilla:en-US:official&#038;q=google reader vs bloglines beta&#038;btnG=Search" rel="nofollow">bloglines beta vs. google reader</a>.  At least, in my view of the search results.  I know position can vary depending on who is searching.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
