<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2009:/1/tag:www.readwriteweb.com,2008://1.5907-</id>
  <updated>2009-11-23T19:20:55Z</updated>
  <title>Comments for Does FriendFeed Solve a Problem, or Highlight One?</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=5907" title="Does FriendFeed Solve a Problem, or Highlight One?" />
    <published>2008-03-18T19:16:55Z</published>
    <updated>2008-03-19T08:27:59Z</updated>
    <title>Does FriendFeed Solve a Problem, or Highlight One?</title>
    <summary>Does FriendFeed Solve Info Overload?</summary>
    <author>
      <name>Josh Catone</name>
      <uri>http://www.readwriteweb.com/</uri>
    </author>
    
    <category term="Attention" />
    
    <category term="Features" />
    
    <category term="Products" />
    
    <category term="Trends" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img src="http://www.readwriteweb.com/images/fflogo.jpg" />Lifestream aggregator-turned-social network <a href="http://www.friendfeed.com/">FriendFeed</a> is the most hyped thing since sliced bread -- or at least the most hyped web app since Twitter.  Among the <a href="http://www.readwriteweb.com/archives/35_lifestreamin_apps.php">scads of lifestreaming apps</a>, FriendFeed has garnered the lions share of recent press and hype among early adopters.  The promise of lifestreaming is that it can bring all the various activity streams from the friends that you follow at multiple services under a single umbrella, vastly simplifying your information overloaded Internet existence. But do services like FriendFeed really solve the problem, or just highlight it? Can they even add to it?</p>]]>
      <![CDATA[<p>We've definitely contributed to some of the hype around FriendFeed on this blog: we picked it as a <a href="http://www.readwriteweb.com/archives/sxsw_breakout_app_of_2008.php">potential breakout app at SXSW</a>, and we <a href="http://www.readwriteweb.com/archives/friendfeed.php">backed it over a competing high profile lifestream app</a>.  But given the results so far to <a href="http://www.readwriteweb.com/archives/poll_are_you_using_friendfeed.php">this week's poll</a> (you can vote below), there is clearly a big market for lifestream aggregators (64% of respondents say they use some sort of lifestreaming app).</p>

<h2>Information Overload</h2>

<p>But while FriendFeed and similar services bring activity streams into a single place, making it easier to keep track of your friend's activity, there's still an overwhelming amount of activity for most of us to track.  I follow just a handful of people <a href="http://twitter.com/catone">on Twitter</a>, and already the stream of activity is fast and furious.  The same applies to the activity of my hundreds of friends on Facebook.  Add into that activity from tens of other accounts and you can imagine how quickly an aggregated feed of your friends' activity can become overwhelming.</p>

<p><img src="http://www.readwriteweb.com/images/friendfeed2.jpg" /> </p> 

<p>FriendFeed definitely does some things to alleviate the flow of information.  For example, it groups similar items together -- i.e., rather than sending the 50 Flickr images that you just uploaded or the 50 tweets you just made at Twitter to your stream individually, it sends one or two with a link to the rest.  FriendFeed also <a href="http://blog.friendfeed.com/2008/03/friendfeed-has-search.html">added search</a> yesterday, which is a very useful feature allowing people to see what their friends are doing around specific topics across multiple networks.</p>

<p>FriendFeed tracks 28 services.  <a href="http://www.profilactic.com/">Profilactic</a>, another lifestreaming application, supports <i>155</i>.  <a href="http://scobleizer.com/2008/03/17/how-many-services-do-we-need/">Robert Scoble asked</a> yesterday, how many services do we need?  Good question.  While FriendFeed certainly makes it easier to track your friends activity at all those services, it also exposes you to all of them.  Before if you wanted to follow Joe on Twitter and Facebook, you followed him on Twitter and Facebook.  If you follow him on FriendFeed, you also follow Joe on Flickr, and Netflix, and Amazon, and MySpace, and Pownce, and Digg, and YouTube, and every other service he might use.  Yikes! (Note: there are some <a href="http://fastwonderblog.com/2008/03/18/friendfeed-minus-twitter/">third party hacks</a> to get around this.)</p>

<h2>Adding To The Problem</h2>

<p>Generally, FriendFeed highlights the problem of information overload, but it also has a hand in contributing to it.  We all thought we were signing up for a social activity aggregator, but BAM!, turns out FriendFeed is a social network in its own right.  FriendFeed encourages people to comment on items sent through its feeds <i>on FriendFeed</i> rather than on the source site.  Some people think this is a <a href="http://www.louisgray.com/live/2008/03/duncan-riley-misses-point-of-friendfeed.html">killer feature</a> that focuses conversations around all of our activity, while others think that it fragments conversations and could <a href="http://www.webware.com/8301-1_109-9896535-2.html?part=rss&tag=feed&subj=Webware">lead to redundancy</a> as a result of "Social Network Switching Decay."</p>

<p>What it really might do is add to the noise.  Lifestreaming services like FriendFeed that aggregate our social activity are supposed to be about making things simpler and lessening information overload -- not about adding to the flow of information.</p>

<h2>What We Need</h2>

<p><img src="http://www.readwriteweb.com/images/friendfeedscreen.jpg" align="right" hspace="5px" vspace="5px">In an <a href="http://www.readwriteweb.com/archives/attention_economy_overview.php">attention economy</a> information overload is a serious concern.  Services that can aggregate activity streams -- things that command a lot of our attention -- and make sorting through all that information easier are welcome.  FriendFeed has the potential to be a very useful service in this area, but it needs a few tweaks, in my opinion.</p>

<p><b>First</b>, it needs filters.  As <a href="http://blog.webreakstuff.com/2008/03/friendfeed-cute-but-not-helping/">Fred Oliveira wrote</a>, "If I already have Twitteriffic on, It makes sense to be able to filter out all Twitter bits from my friendfeed. If I’m in the mood for checking out photos from friends, I may want to see only photos on my friendfeed. If I’m looking for what my friends have been listening to on Last.fm, I might want to see only that."</p>

<p>Search was a good first step, but service and keyword based filters that give users more granular control over what sort of information is shown on their friends feed are a necessary next step.  Filters could perhaps even be implemented on a friend-by-friend basis, and maybe automatic and weighted based on reading habits -- similar to Facebook's News Feed.</p>

<p>Filters would help us to actually <i>reduce</i> the amount of information we're tracking and remove noise from our feeds.</p> 

<p><b>Second</b>, FriendFeed needs to be a read/write service.  Not in the way it is now, but by letting users write to the services they're pulling from.  If I want to reply to a tweet, I don't want to do it on FriendFeed, I want to do it at the source: Twitter.  Allowing me to do so from within FriendFeed would be awesome.</p>

<p><b>Third</b>, FriendFeed needs an API (supposedly <a href="http://scobleizer.com/2008/03/17/friendfeed-searches-for-an-api/">this is coming</a>).  While you shouldn't let your customers run your app, you should let your users <a href="http://www.readwriteweb.com/archives/let_users_define_your_app.php">define your application</a>.  Allowing developers to build on top of and extend the functionality of your application via mashups is often how good applications become killer applications. Without the ecosystem of awesome Twitter applications, for example, the service might not be nearly as fun to use and useful.</p>

<h2>Conclusion</h2>

<p>It is no wonder that FriendFeed has become the early breakout app of 2008.  It has the potential to be truly useful, but right now it is doing more to highlight the problem of information overload -- and even add to it -- than it is to solve the problem.  However, the promise of an application that can help us crawl out from under the constant stream of information that has inundated our lives is what makes FriendFeed, and similar services, so intriguing.</p>

<p>What do you think? Is FriendFeed a killer app as-is?  Has it already helped your to cope with info overload?  Let us know in the comments below, and be sure to vote in our poll.</p>

<p><script type="text/javascript" language="javascript" src="http://s3.polldaddy.com/p/428252.js"></script><noscript> <a href ="http://www.polldaddy.com" >polls</a> - <a href ="http://answers.polldaddy.com/poll/428252/" >Take Our Poll</a> </noscript></p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49618</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49618" />
    <title>Comment from Varun Mahajan on 2008-03-18</title>
    <author>
        <name>Varun Mahajan</name>
        <uri>http://varunmayan.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://varunmayan.blogspot.com">
        <![CDATA[<p>Give them some time. After all they are ex-googlers. They know what world wants</p>]]>
    </content>
    <published>2008-03-18T20:55:15Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49619</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49619" />
    <title>Comment from Perry Mizota on 2008-03-18</title>
    <author>
        <name>Perry Mizota</name>
        <uri>http://abovethenoise.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://abovethenoise.blogspot.com">
        <![CDATA[<p>If you view FriendFeed as purely a stream of information, I agree with your perspective.  However, if you view the information collected by FriendFeed as a corpus of data that can be leveraged in the future, I think the implications - and benefits - of such a service is much broader, and why I feel the search capability announced by FriendFeed last night is significant.</p>

<p>I have been a big fan of a concept I call "knowledge networking".  This is the ability to leverage the knowledge of your friends and colleagues.  I feel that FriendFeed's search capability brings this concept one step closer to reality.</p>

<p>More details on my thoughts can be found at <a href="http://tinyurl.com/2ny56a." rel="nofollow">http://tinyurl.com/2ny56a.</a><br />
</p>]]>
    </content>
    <published>2008-03-18T20:55:27Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49622</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49622" />
    <title>Comment from abhi on 2008-03-18</title>
    <author>
        <name>abhi</name>
        <uri>http://www.digitalpurview.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.digitalpurview.com/">
        <![CDATA[<p>It's tool early to comment on these guys. Platform is only as strong as users. </p>]]>
    </content>
    <published>2008-03-18T21:15:56Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49627</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49627" />
    <title>Comment from Steven Hodson on 2008-03-18</title>
    <author>
        <name>Steven Hodson</name>
        <uri>http://www.winextra.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.winextra.com">
        <![CDATA[<p>You point about seeing all that "Joe" is connected to is easily fixed by clicking on the Options link under any of Joe's postsing that show up in FriendFeed and click on the Hide Entries Like This.</p>

<p>This way you can hide Joe's Twitter posts or Flickr postings etc.</p>]]>
    </content>
    <published>2008-03-18T21:27:57Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49631</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49631" />
    <title>Comment from chris on 2008-03-18</title>
    <author>
        <name>chris</name>
        <uri>http://chrispeoples.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://chrispeoples.com">
        <![CDATA[<p>Some of that filtering is already available.  On each item, if click options, you can "<a href="http://groups.google.com/group/friendfeed/msg/44b0c86686977f12" rel="nofollow">hide entries like these</a>".</p>]]>
    </content>
    <published>2008-03-18T21:40:41Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49636</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49636" />
    <title>Comment from Vyrotek on 2008-03-18</title>
    <author>
        <name>Vyrotek</name>
        <uri>http://www.vyrotek.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.vyrotek.com">
        <![CDATA[<p>For these types of services to be useful you actually need people who care about all these little things youre doing. And of course if im one of those people interested I need my friend to have a friendfeed already available.</p>

<p>There are some things Id like to know about my friends, but only when they proactively want to share it with me. If they went out of their way to share it with me then its probably something good.</p>

<p>We need to take a step back and think about WHY we are trying to share this stuff with someone. I know I would eventually get sick of someone sharing too much stuff freely with me that I didnt care about.</p>

<p>Im not sure where the line is best drawn between automatic data tracking/sharing and proactively selecting certain things to share with certain people. Perhaps the problem is solved by letting me filter what kind of data I want to know.</p>]]>
    </content>
    <published>2008-03-18T22:19:31Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49637</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49637" />
    <title>Comment from Vyrotek on 2008-03-18</title>
    <author>
        <name>Vyrotek</name>
        <uri>http://www.vyrotek.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.vyrotek.com">
        <![CDATA[<p>So I had this post up for a long time and didnt refresh to see the comments about the filtering. Sure, you could say hide these types... but that doesnt solve the problem. I might want to know when they upload a flicker photo when its something I would be interested in, but not all the time. By saying hide that kind of item I wont ever know about it unless now I go UNhide that kind of data. </p>

<p>Maybe the solution is to actually create filters for each one of your friends are subscribed. YOu custom taylor your feed to each one of your friends. Sure, a bit more work... but it adds a WHOLE lot more value.</p>]]>
    </content>
    <published>2008-03-18T22:27:52Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49646</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49646" />
    <title>Comment from mabisa on 2008-03-18</title>
    <author>
        <name>mabisa</name>
        <uri>http://mabisa.org/blog</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://mabisa.org/blog">
        <![CDATA[<p>I think your second point is most significant and has been my problem with previous lifestreaming applications; it is far too time-consuming to click through to flickr/twitter/facebook/what-have-you in order to have a decent level of meaningful interaction. As social applications, that sort of rich interaction is where value lies. To me, a true lifestreaming application would be far more robust in its read/write capabilities. It alarms me that at this point these companies do not premiere with that sort of openness (or, similarly, an API) at launch.</p>]]>
    </content>
    <published>2008-03-18T23:40:36Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49650</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49650" />
    <title>Comment from Slim Amamou on 2008-03-18</title>
    <author>
        <name>Slim Amamou</name>
        <uri>http://NoMemorySpace.wordpress.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://NoMemorySpace.wordpress.com">
        <![CDATA[<p>there are two kinds of searches : searching for something you never knew (that's google) and searching for something you actually knew (that's what friendfeed wants to be)</p>

<p>friendfeed, like soup.io and others, has to do with "history publication" and its counterpart "memory management" (in the anatomical sense, not the OS sense). </p>

<p>people will need to manage their history as history is the basis of trust and authority. thus literally keeping control of their own history. </p>

<p>but they will also want to manage portions of other peoples histories. friends or enemies.  thus accumulating huge amounts of their own experience data. </p>

<p>obviously they will need search. </p>]]>
    </content>
    <published>2008-03-19T01:15:14Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49654</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49654" />
    <title>Comment from smorty71 on 2008-03-18</title>
    <author>
        <name>smorty71</name>
        <uri>http://www.profilactic.com/mashup/smorty71</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.profilactic.com/mashup/smorty71">
        <![CDATA[<p>Josh, thanks for mentioning Profilactic. We appreciate it.</p>

<p>Wanted to mention that Profilactic allows you to filter out feeds from the friends you follow. So if you don't want to follow someone's Flickr photos, you can exclude those.</p>]]>
    </content>
    <published>2008-03-19T02:30:20Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49656</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49656" />
    <title>Comment from Dawn Foster on 2008-03-18</title>
    <author>
        <name>Dawn Foster</name>
        <uri>http://fastwonderblog.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://fastwonderblog.com">
        <![CDATA[<p>Thanks for the link to my FriendFeed Minus Twitter hack!</p>

<p>I am a bit annoyed by the ability to comment on FriendFeed content.  I would much rather have someone comment directly on my blog, Flickr, or whatever. I tend to think that it just fragments the conversations, and I end up missing things.</p>]]>
    </content>
    <published>2008-03-19T03:17:11Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49657</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49657" />
    <title>Comment from Olivier Duprez alias ze kat on 2008-03-18</title>
    <author>
        <name>Olivier Duprez alias ze kat</name>
        <uri>http://life2front.com/oliezekat</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://life2front.com/oliezekat">
        <![CDATA[<p>Lifestreaming is not a joke. That's why I study on this problem since one year...</p>

<p>LiFE2Front's LiFE-Line system purpose "instant" search/filter engine. And my friendstream product named Seek-Line will use same UI.<br />
<a href="http://www.life2front.com/seek-line/" rel="nofollow">http://www.life2front.com/seek-line/</a></p>

<p>Sorry, beta-recruitment is closed while 2 month. Join our MyBlogLog community ;o)</p>]]>
    </content>
    <published>2008-03-19T04:05:04Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49663</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49663" />
    <title>Comment from Jack Carlson on 2008-03-18</title>
    <author>
        <name>Jack Carlson</name>
        <uri>https://friendfeed.com/jeber</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="https://friendfeed.com/jeber">
        <![CDATA[<p>I agree it's a bit soon to be expecting a finished and full-featured product.  I also think critiques like this are a valuable source of inspiration for the developers.  It's a bit like Open Sourcing a proprietary application to listen to and be directed by your users.  </p>

<p>Applications like FriendFeed and Twitter have the potential to push the social aspects of the internet in new directions by providing unique opportunities for us all to interact. If they pay attention to the suggestions of their users, they may well become the next big thing.  If they don't, they may have a sock puppet on their hands.  </p>]]>
    </content>
    <published>2008-03-19T06:08:06Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49664</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49664" />
    <title>Comment from bg on 2008-03-18</title>
    <author>
        <name>bg</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I've been using Iminta for a few months now and does a great job of addressing your first point. It allows filters on content type, content source, friends, friend groups or any combination.</p>

<p>They doesn't have an API, but they do provide filterable RSS.</p>]]>
    </content>
    <published>2008-03-19T06:15:43Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49666</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49666" />
    <title>Comment from Tal Keinan on 2008-03-19</title>
    <author>
        <name>Tal Keinan</name>
        <uri>http://www.semantinet.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.semantinet.com">
        <![CDATA[<p>The problem with commenting taking place away from the source is that over time it weakens the source. I see the great benefit for friendfeed in doing so, but at the end of the day, friendfeed is "feeding" off these services, so it is in their best interest to ensure their long-term success.</p>]]>
    </content>
    <published>2008-03-19T07:10:51Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49672</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49672" />
    <title>Comment from Marina martin on 2008-03-19</title>
    <author>
        <name>Marina martin</name>
        <uri>http://www.marinamartin.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.marinamartin.com">
        <![CDATA[<p>The inherent problem with FriendFeed or any other of the currently-available lifestreaming services is that it relies on each user reliably updating their own information.</p>

<p>This is a problem. I have a FriendFeed stream that I never update with new services or to edit out old ones. In fact, it's very possible that my current FriendFeed has a Jaiku stream of my Twitter AND a Twitter stream of my Twitter. Oops.</p>

<p>This is my main problem with services like Plaxo, too. (That, and Plaxo gives me the heebie-jeebies.) I'm an efficiency consultant. I know how unorganized my clients are. I would never trust them to update Plaxo with their new mobile number. I do, however, trust myself to update (and backup) my phone book with their new number.</p>

<p>I want a FriendFeed where *I* define which feeds I receive for each person. That would rock.</p>

<p>Also, my use of a lifestreaming service would not be for getting constant updates on people. Rather, I'd use it for a quick briefing on what someone's up to before getting [back] in touch with them.</p>]]>
    </content>
    <published>2008-03-19T09:05:21Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5907-comment:49760</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5907" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/friendfeed_information_overload.php#c49760" />
    <title>Comment from Dawn Foster on 2008-03-19</title>
    <author>
        <name>Dawn Foster</name>
        <uri>http://fastwonderblog.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://fastwonderblog.com">
        <![CDATA[<p>I've hacked together a FriendFeed Comment Finder using Yahoo Pipes that people can use to get FriendFeed Comments as an RSS feed. Still in the experimental and might break phase :-)<br />
<a href="http://tinyurl.com/ys92bs" rel="nofollow">http://tinyurl.com/ys92bs</a><br />
</p>]]>
    </content>
    <published>2008-03-20T06:04:22Z</published>
  </entry>

</feed>