<?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: Review: Spokeo, a social network aggregator</title>
	<atom:link href="http://comments.deasil.com/2007/09/07/review-spokeo-a-social-network-aggregator/feed/" rel="self" type="application/rss+xml" />
	<link>http://comments.deasil.com/2007/09/07/review-spokeo-a-social-network-aggregator/</link>
	<description>escape colon w q</description>
	<pubDate>Mon, 01 Dec 2008 19:17:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: felix</title>
		<link>http://comments.deasil.com/2007/09/07/review-spokeo-a-social-network-aggregator/#comment-4485</link>
		<dc:creator>felix</dc:creator>
		<pubDate>Fri, 07 Sep 2007 20:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/09/07/review-spokeo-a-social-network-aggregator/#comment-4485</guid>
		<description>Harrison, yeah, that's exactly the sort of audience I thought this product would be good for! But, beyond that I think your interface wouldn't need much to start serving a more heavy usage audience (i.e. me :). Very broadly just two things, if you tweaked the "overview" screen so that it behaved a little more like google reader where it's quick hits that you can expand down. And giving a means to view all the unread stuff across feeds. From a UI perspective I think that would not be too big a departure - since all the components are pretty much already there. Other stuff like more group functionality would be icing on the cake. :) Please don't think I'm suggesting you should throw away your current design!</description>
		<content:encoded><![CDATA[<p>Harrison, yeah, that&#8217;s exactly the sort of audience I thought this product would be good for! But, beyond that I think your interface wouldn&#8217;t need much to start serving a more heavy usage audience (i.e. me :). Very broadly just two things, if you tweaked the &#8220;overview&#8221; screen so that it behaved a little more like google reader where it&#8217;s quick hits that you can expand down. And giving a means to view all the unread stuff across feeds. From a UI perspective I think that would not be too big a departure - since all the components are pretty much already there. Other stuff like more group functionality would be icing on the cake. :) Please don&#8217;t think I&#8217;m suggesting you should throw away your current design!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harrison</title>
		<link>http://comments.deasil.com/2007/09/07/review-spokeo-a-social-network-aggregator/#comment-4483</link>
		<dc:creator>Harrison</dc:creator>
		<pubDate>Fri, 07 Sep 2007 20:13:24 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/09/07/review-spokeo-a-social-network-aggregator/#comment-4483</guid>
		<description>Thank you for writing this extensive review on Spokeo.  Your feedback gives us a lot of insights, and we are going to evaluate each one of them in our next design meeting.

Our design goal is different from any other RSS reader, since we can syndicate non-RSS multimedia.  We are built for casual reading, so we try very hard to stay away from complicated feed management.  We want our users to come and get a glimpse of their networks' updates, then they can just move on.

This is why we don't give our users too many options.  Our users don't need to care about advanced functionalities, and they probably don't.  We decide and stick with the default, and this is why our UI is so much cleaner than any other reader out there.

It's like IPod vs. other MP3 players.  IPod does not have FM/AM support, or recording sounds, or any of other jazz.  However, because they don't have to integrate these peripheral features, IPod is the easiest to use.  Spokeo is the same.  We are here to aggregate and syndicate information, so our focus lies in syndicate broader content, and do it faster.  We are not here to enable people to share or comment.

Of course, our decisions on the default design can be wrong.  This is where our user feedbacks come in, and this is why we thank you for writing this extensive review.  We will seriously think about your suggestions, and if they make sense, we will throw away our current design and make yours our current default :)</description>
		<content:encoded><![CDATA[<p>Thank you for writing this extensive review on Spokeo.  Your feedback gives us a lot of insights, and we are going to evaluate each one of them in our next design meeting.</p>
<p>Our design goal is different from any other RSS reader, since we can syndicate non-RSS multimedia.  We are built for casual reading, so we try very hard to stay away from complicated feed management.  We want our users to come and get a glimpse of their networks&#8217; updates, then they can just move on.</p>
<p>This is why we don&#8217;t give our users too many options.  Our users don&#8217;t need to care about advanced functionalities, and they probably don&#8217;t.  We decide and stick with the default, and this is why our UI is so much cleaner than any other reader out there.</p>
<p>It&#8217;s like IPod vs. other MP3 players.  IPod does not have FM/AM support, or recording sounds, or any of other jazz.  However, because they don&#8217;t have to integrate these peripheral features, IPod is the easiest to use.  Spokeo is the same.  We are here to aggregate and syndicate information, so our focus lies in syndicate broader content, and do it faster.  We are not here to enable people to share or comment.</p>
<p>Of course, our decisions on the default design can be wrong.  This is where our user feedbacks come in, and this is why we thank you for writing this extensive review.  We will seriously think about your suggestions, and if they make sense, we will throw away our current design and make yours our current default :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
