<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How to build the mesh - #4: the Live Web</title>
	<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web</link>
	<description>Digital Lifestyle Aggregation - helping to establish open source infrastructure</description>
	<pubDate>Fri, 04 Jul 2008 20:05:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; I do not compromise</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-246083</link>
		<author>Marc&#8217;s Voice &#187; Blog Archive &#187; I do not compromise</author>
		<pubDate>Fri, 16 May 2008 21:02:25 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-246083</guid>
		<description>[...] the Live Web - we can&#8217;t live without my Twitter, IM, FriendFeed, VoIP, Second Life, mobile phone and [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] the Live Web - we can&#8217;t live without my Twitter, IM, FriendFeed, VoIP, Second Life, mobile phone and [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the Open Mesh</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245706</link>
		<author>Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the Open Mesh</author>
		<pubDate>Fri, 02 May 2008 19:15:58 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245706</guid>
		<description>[...] [4] - the Live Web [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] [4] - the Live Web [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the mesh - #8: Common Constructs, Verbs and Pages</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245694</link>
		<author>Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the mesh - #8: Common Constructs, Verbs and Pages</author>
		<pubDate>Fri, 02 May 2008 16:58:36 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245694</guid>
		<description>[...] set of constructs are in the area of - #4 - Live Web  - message (a short blip of communication, can also be used to refer to private emails inside of [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] set of constructs are in the area of - #4 - Live Web  - message (a short blip of communication, can also be used to refer to private emails inside of [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the mesh - #7: Infrastructure</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245665</link>
		<author>Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the mesh - #7: Infrastructure</author>
		<pubDate>Thu, 01 May 2008 23:31:57 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245665</guid>
		<description>[...] areas of &#8220;How to build the mesh&#8221; and what I was hoping for - paid off. [1], [2], [3], [4], [5], [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] areas of &#8220;How to build the mesh&#8221; and what I was hoping for - paid off. [1], [2], [3], [4], [5], [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the mesh - #5: Tools</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245624</link>
		<author>Marc&#8217;s Voice &#187; Blog Archive &#187; How to build the mesh - #5: Tools</author>
		<pubDate>Wed, 30 Apr 2008 20:46:55 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245624</guid>
		<description>[...] Tools are a key aspect of my design of this series of &#8220;How to build the mesh&#8221; blog posts and we can now see how all the pieces of the puzzle can come together. As long as we [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Tools are a key aspect of my design of this series of &#8220;How to build the mesh&#8221; blog posts and we can now see how all the pieces of the puzzle can come together. As long as we [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blaine Cook</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245623</link>
		<author>Blaine Cook</author>
		<pubDate>Wed, 30 Apr 2008 20:42:20 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245623</guid>
		<description>Hey there, just a few people to add to your "people to watch" --- hopefully myself (I built all the jabber infrastructure at Twitter, and built a prototype federation model with Jaiku before I left) and definitely Ralph Meijer who has been long advocating and designing the Jabber PubSub specs. Peter Saint-Andre is the overseer of the XMPP specs, and a great guy besides. The Jive and ejabberd (Process-One) folks are doing some great things, too.

The one point that I see missing from your discussion that's absolutely critical is addressability. It's implicit, I think, in your discussion, but it's worthwhile drawing it out. What we're going to see in the next year or so is a shift from social networks as walled gardens --- I think of it as the transition from email-as-AOL-and-CompuServe to email-as-federated-by-SMTP.</description>
		<content:encoded><![CDATA[<p>Hey there, just a few people to add to your &#8220;people to watch&#8221; &#8212; hopefully myself (I built all the jabber infrastructure at Twitter, and built a prototype federation model with Jaiku before I left) and definitely Ralph Meijer who has been long advocating and designing the Jabber PubSub specs. Peter Saint-Andre is the overseer of the XMPP specs, and a great guy besides. The Jive and ejabberd (Process-One) folks are doing some great things, too.</p>
<p>The one point that I see missing from your discussion that&#8217;s absolutely critical is addressability. It&#8217;s implicit, I think, in your discussion, but it&#8217;s worthwhile drawing it out. What we&#8217;re going to see in the next year or so is a shift from social networks as walled gardens &#8212; I think of it as the transition from email-as-AOL-and-CompuServe to email-as-federated-by-SMTP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; My summer project - works-in-progress</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245613</link>
		<author>Marc&#8217;s Voice &#187; Blog Archive &#187; My summer project - works-in-progress</author>
		<pubDate>Wed, 30 Apr 2008 16:44:14 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245613</guid>
		<description>[...] &#171; How to build the mesh - #4: the Live Web [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] &laquo; How to build the mesh - #4: the Live Web [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kip</title>
		<link>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245611</link>
		<author>kip</author>
		<pubDate>Wed, 30 Apr 2008 16:42:32 +0000</pubDate>
		<guid>http://blog.broadbandmechanics.com/2008/04/how-to-build-the-mesh-4-the-live-web#comment-245611</guid>
		<description>Nice, I like the concept of "the Live Web".  Don't forget in your analysis the real desire and necessity to "go offline", either for short periods of a lack of connectivity, or longer sessions of user initiated "unplugging".

The Live Web will enable, but it will also tether.  Google is pushing for free and open tools, precisely so that is compelling to be connected early and often.  Will part of our "data portability", our ownership of our experience, allow us to unplug as well as plug in anywhere and everywhere?  Will we be able to catch up?  Will our online experience suffer holes of inactivity, or will the Live Web "fill in" our experiences?

Interested to continue following the conversation, Marc.  Good post.</description>
		<content:encoded><![CDATA[<p>Nice, I like the concept of &#8220;the Live Web&#8221;.  Don&#8217;t forget in your analysis the real desire and necessity to &#8220;go offline&#8221;, either for short periods of a lack of connectivity, or longer sessions of user initiated &#8220;unplugging&#8221;.</p>
<p>The Live Web will enable, but it will also tether.  Google is pushing for free and open tools, precisely so that is compelling to be connected early and often.  Will part of our &#8220;data portability&#8221;, our ownership of our experience, allow us to unplug as well as plug in anywhere and everywhere?  Will we be able to catch up?  Will our online experience suffer holes of inactivity, or will the Live Web &#8220;fill in&#8221; our experiences?</p>
<p>Interested to continue following the conversation, Marc.  Good post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
