<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Wave on Slow Cook</title>
	<atom:link href="http://firstwaves.org/wave-on-slow-cook/feed/" rel="self" type="application/rss+xml" />
	<link>http://firstwaves.org/wave-on-slow-cook/</link>
	<description>Examining Google+ as it Grows</description>
	<lastBuildDate>Thu, 14 Jul 2011 17:42:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: A Bunch of Stuff &#171; Josh Nunn&#039;s Geekorium</title>
		<link>http://firstwaves.org/wave-on-slow-cook/#comment-30</link>
		<dc:creator>A Bunch of Stuff &#171; Josh Nunn&#039;s Geekorium</dc:creator>
		<pubDate>Tue, 30 Mar 2010 11:47:03 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477507#comment-30</guid>
		<description>[...] Waves is going great-guns. tjb654 tweeted “Wave on Slow Cook” and was retweeted by Pamela Fox (one of the Wave API evangelists). So I got a bunch of new [...]</description>
		<content:encoded><![CDATA[<p><span class="caps">API </span>evangelists). So IÂ got aÂ bunch of new […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://firstwaves.org/wave-on-slow-cook/#comment-29</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 26 Mar 2010 21:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477507#comment-29</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by firstwaves: First Waves Update: Wave on Slow Cook http://e01.li/dnrxi7...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post…</strong></p>
<p>This post was mentioned on Twitter by firstwaves: First Waves Update: Wave on Slow Cook <a href="http://e01.li/dnrxi7&#8230;" rel="nofollow">http://e01.li/dnrxi7…</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention First Waves » Wave on Slow Cook -- Topsy.com</title>
		<link>http://firstwaves.org/wave-on-slow-cook/#comment-28</link>
		<dc:creator>Tweets that mention First Waves » Wave on Slow Cook -- Topsy.com</dc:creator>
		<pubDate>Fri, 26 Mar 2010 21:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477507#comment-28</guid>
		<description>[...] This post was mentioned on Twitter by pamelafox and Marty Nostrala, Timothy Brown. Timothy Brown said: I appreciate this perspective on Google Wave: http://goo.gl/vN3a #googlewave [...]</description>
		<content:encoded><![CDATA[<p>[…] This post was mentioned on Twitter by pamelafox and Marty Nostrala, Timothy Brown. Timothy Brown said: I appreciate this perspective on Google Wave: <a href="http://goo.gl/vN3a" rel="nofollow">http://goo.gl/vN3a</a> #googlewave […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joshnunn</title>
		<link>http://firstwaves.org/wave-on-slow-cook/#comment-27</link>
		<dc:creator>joshnunn</dc:creator>
		<pubDate>Tue, 16 Mar 2010 17:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477507#comment-27</guid>
		<description>You&#039;re exactly right. And while all the robots etc are somewhat limited at the moment, it&#039;s easy to imagine bots and gadgets that help integrate all sorts of other comminucation into Wave - for those of use who want that.&lt;br&gt;&lt;br&gt;As for the horizontal communication, I suspect that Google are working on that. The recent API update has shown that this is where it&#039;s all headed eventually. It&#039;s just baby steps all the way. And people forget that this is the way Google works. None of their most successful products started out the powerhouses they are today, they grew slowly over time. The same philosophy applies doubly to Wave.&lt;br&gt;&lt;br&gt;Thanks for your insights. I appreciate you taking the time to comment!</description>
		<content:encoded><![CDATA[<p>You’re exactly right. And while all the robots etc are somewhat limited at the moment, it’s easy to imagine bots and gadgets that help integrate all sorts of other comminucation into Wave – for those of use who want that.</p>
<p>As for the horizontal communication, I suspect that Google are working on that. The recent <span class="caps">API </span>update has shown that this is where it’s all headed eventually. It’s just baby steps all the way. And people forget that this is the way Google works. None of their most successful products started out the powerhouses they are today, they grew slowly over time. The same philosophy applies doubly to Wave.</p>
<p>Thanks for your insights. I appreciate you taking the time to comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://firstwaves.org/wave-on-slow-cook/#comment-26</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Tue, 16 Mar 2010 17:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477507#comment-26</guid>
		<description>I do wish people would stop talking as though their failure to understand what Wave is all about is a failure of Wave in the &quot;marketplace&quot;.&lt;br&gt;I have no problem visualising Wave as a replacement for email, as it stands; in some cases, existing friends have moved over to using it for much that purpose already.&lt;br&gt;&lt;br&gt;Arguably the plethora of little robots and extensions can become a gimmick, especially if people think the things they do should be done in the underlying platform. The flip-side is that Wave has to bring something useful to sites that try to make themselves visible on it.&lt;br&gt;&lt;br&gt;The main problem I see with the platform is that it is too cartesian: it&#039;s a simple framework of waves and blips and whatnots, and either you&#039;re an extension in which case you live entirely within a blip or you&#039;re a robot in which case you&#039;re entirely within a wave. There&#039;s not enough horizontal communication to blur between the two modes of operation.</description>
		<content:encoded><![CDATA[<p>I do wish people would stop talking as though their failure to understand what Wave is all about is a failure of Wave in the “marketplace”.<br />I have no problem visualising Wave as a replacement for email, as it stands; in some cases, existing friends have moved over to using it for much that purpose already.</p>
<p>Arguably the plethora of little robots and extensions can become a gimmick, especially if people think the things they do should be done in the underlying platform. The flip-side is that Wave has to bring something useful to sites that try to make themselves visible on it.</p>
<p>The main problem I see with the platform is that it is too cartesian: it’s a simple framework of waves and blips and whatnots, and either you’re an extension in which case you live entirely within a blip or you’re a robot in which case you’re entirely within a wave. There’s not enough horizontal communication to blur between the two modes of operation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Screenbeard</title>
		<link>http://firstwaves.org/wave-on-slow-cook/#comment-92</link>
		<dc:creator>Screenbeard</dc:creator>
		<pubDate>Tue, 16 Mar 2010 12:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477507#comment-92</guid>
		<description>You&#039;re exactly right. And while all the robots etc are somewhat limited at the moment, it&#039;s easy to imagine bots and gadgets that help integrate all sorts of other comminucation into Wave - for those of use who want that.

As for the horizontal communication, I suspect that Google are working on that. The recent API update has shown that this is where it&#039;s all headed eventually. It&#039;s just baby steps all the way. And people forget that this is the way Google works. None of their most successful products started out the powerhouses they are today, they grew slowly over time. The same philosophy applies doubly to Wave.

Thanks for your insights. I appreciate you taking the time to comment!</description>
		<content:encoded><![CDATA[<p>You’re exactly right. And while all the robots etc are somewhat limited at the moment, it’s easy to imagine bots and gadgets that help integrate all sorts of other comminucation into Wave – for those of use who want that.</p>
<p>As for the horizontal communication, I suspect that Google are working on that. The recent <span class="caps">API </span>update has shown that this is where it’s all headed eventually. It’s just baby steps all the way. And people forget that this is the way Google works. None of their most successful products started out the powerhouses they are today, they grew slowly over time. The same philosophy applies doubly to Wave.</p>
<p>Thanks for your insights. I appreciate you taking the time to comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://firstwaves.org/wave-on-slow-cook/#comment-91</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Tue, 16 Mar 2010 12:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477507#comment-91</guid>
		<description>I do wish people would stop talking as though their failure to understand what Wave is all about is a failure of Wave in the &quot;marketplace&quot;.
I have no problem visualising Wave as a replacement for email, as it stands; in some cases, existing friends have moved over to using it for much that purpose already.

Arguably the plethora of little robots and extensions can become a gimmick, especially if people think the things they do should be done in the underlying platform. The flip-side is that Wave has to bring something useful to sites that try to make themselves visible on it.

The main problem I see with the platform is that it is too cartesian: it&#039;s a simple framework of waves and blips and whatnots, and either you&#039;re an extension in which case you live entirely within a blip or you&#039;re a robot in which case you&#039;re entirely within a wave. There&#039;s not enough horizontal communication to blur between the two modes of operation.</description>
		<content:encoded><![CDATA[<p>I do wish people would stop talking as though their failure to understand what Wave is all about is a failure of Wave in the “marketplace”.<br />
I have no problem visualising Wave as a replacement for email, as it stands; in some cases, existing friends have moved over to using it for much that purpose already.</p>
<p>Arguably the plethora of little robots and extensions can become a gimmick, especially if people think the things they do should be done in the underlying platform. The flip-side is that Wave has to bring something useful to sites that try to make themselves visible on it.</p>
<p>The main problem I see with the platform is that it is too cartesian: it’s a simple framework of waves and blips and whatnots, and either you’re an extension in which case you live entirely within a blip or you’re a robot in which case you’re entirely within a wave. There’s not enough horizontal communication to blur between the two modes of operation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

