<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Geek Estate Blog - Latest Comments in A Normal Morning, then Open Up MyBlogLog and&amp;#8230;Lifestreaming</title><link>http://geekestateblog.disqus.com/</link><description>Real estate technology news and analysis</description><atom:link href="https://geekestateblog.disqus.com/a_normal_morning_then_open_up_mybloglog_and8230lifestreaming/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 19 Mar 2008 14:54:04 -0000</lastBuildDate><item><title>Re: A Normal Morning, then Open Up MyBlogLog and&amp;#8230;Lifestreaming</title><link>http://geekestateblog.com/a-normal-morning-then-open-up-mybloglog-andlifestreaming/#comment-12592625</link><description>&lt;p&gt;I also noticed that MyBlogLog added &lt;a href="http://FriendFeed.com" rel="nofollow noopener" target="_blank" title="FriendFeed.com"&gt;FriendFeed.com&lt;/a&gt; (another LifeStreaming aggregator) to the list of services.&lt;/p&gt;&lt;p&gt;That sounds like an infinite loop to me. You add your aggregated feed to MLB, then add the MLB aggregated feed RSS to &lt;a href="http://FriendFeed.com" rel="nofollow noopener" target="_blank" title="FriendFeed.com"&gt;FriendFeed.com&lt;/a&gt; and there you go, you got an infinite loop, like the video feedback effect, the one you can create with a video camera and taking a video of the TV screen which is connected to the very same camcorder.&lt;/p&gt;&lt;p&gt;Not that anybody wants to do this on purpose, but it still raises a few conceptual question: who will be the ultimate final destination to see your  aggregated online activities? What happens with the distributed, fragmented communication, like isolated comment islands on these different hubs?&lt;/p&gt;&lt;p&gt;In any case, I am trying this out and see what happens.&lt;/p&gt;&lt;p&gt;&lt;a href="http://friendfeed.com/zszendro" rel="nofollow noopener" target="_blank" title="http://friendfeed.com/zszendro"&gt;http://friendfeed.com/zszendro&lt;/a&gt; &lt;br&gt;and&lt;br&gt;&lt;a href="http://www.mybloglog.com/buzz/members/RealBird/" rel="nofollow noopener" target="_blank" title="http://www.mybloglog.com/buzz/members/RealBird/"&gt;http://www.mybloglog.com/bu...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;are now mutually aggregating each other.&lt;/p&gt;&lt;p&gt;-- Zoltan&lt;br&gt;&lt;a href="http://www.RealBird.com" rel="nofollow noopener" target="_blank" title="http://www.RealBird.com"&gt;http://www.RealBird.com&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">RealBird</dc:creator><pubDate>Wed, 19 Mar 2008 14:54:04 -0000</pubDate></item><item><title>Re: A Normal Morning, then Open Up MyBlogLog and&amp;#8230;Lifestreaming</title><link>http://geekestateblog.com/a-normal-morning-then-open-up-mybloglog-andlifestreaming/#comment-12592624</link><description>&lt;p&gt;Thanks for the kind words Drew. You are correct, we have added two new API calls last night along with the New with Me feature:&lt;/p&gt;&lt;p&gt;member.newwithcontacts&lt;br&gt;member.newwithme&lt;/p&gt;&lt;p&gt;You can read up on all the gory details at:&lt;br&gt;&lt;a href="http://developer.yahoo.com/mybloglog" rel="nofollow noopener" target="_blank" title="http://developer.yahoo.com/mybloglog"&gt;http://developer.yahoo.com/...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Cheers,&lt;/p&gt;&lt;p&gt;Ian&lt;/p&gt;&lt;p&gt;Ian&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Kennedy</dc:creator><pubDate>Sat, 01 Mar 2008 00:58:25 -0000</pubDate></item></channel></rss>