
     <?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: Google Wave&#8217;s two nearly fatal flaws</title>
	<atom:link href="http://futuremediachange.com/2009/11/google-waves-two-nearly-fatal-flaws/feed/" rel="self" type="application/rss+xml" />
	<link>http://futuremediachange.com/2009/11/google-waves-two-nearly-fatal-flaws/</link>
	<description>blogging the intersection of media, technology and the global good</description>
	<lastBuildDate>Mon, 16 Aug 2010 11:49:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: uberVU - social comments</title>
		<link>http://futuremediachange.com/2009/11/google-waves-two-nearly-fatal-flaws/comment-page-1/#comment-87</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Mon, 30 Nov 2009 21:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://futuremediachange.com/?p=761#comment-87</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by jasonwhat: Two fatal flaws that make Google Wave not ready for Prime time at your organization http://bit.ly/7iDXrz...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by jasonwhat: Two fatal flaws that make Google Wave not ready for Prime time at your organization <a href="http://bit.ly/7iDXrz.." rel="nofollow">http://bit.ly/7iDXrz..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jasonwhat</title>
		<link>http://futuremediachange.com/2009/11/google-waves-two-nearly-fatal-flaws/comment-page-1/#comment-85</link>
		<dc:creator>jasonwhat</dc:creator>
		<pubDate>Mon, 30 Nov 2009 18:08:12 +0000</pubDate>
		<guid isPermaLink="false">http://futuremediachange.com/?p=761#comment-85</guid>
		<description>I&#039;m with you in thinking that ultimately it will be a winner and achieve google&#039;s goal of making separate tools obsolete. I still think not including some level of Gmail/email integration out of the gate is a killer.  That said, they did release many more invites so the ranks of users will grow quickly.  I&#039;m curious how this will get built into their hosted for business services.&lt;br&gt;&lt;br&gt;Also, as you posted, there are great uses for Wave beyond collaboration that include embedding Waves on websites to super size comments.&lt;br&gt;&lt;a href=&quot;http://futuremediachange.com/2009/11/how-news-organizations-are-using-google-wave/&quot; rel=&quot;nofollow&quot;&gt;http://futuremediachange.com/2009/11/how-news-o...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I&#39;m with you in thinking that ultimately it will be a winner and achieve google&#39;s goal of making separate tools obsolete. I still think not including some level of Gmail/email integration out of the gate is a killer.  That said, they did release many more invites so the ranks of users will grow quickly.  I&#39;m curious how this will get built into their hosted for business services.</p>
<p>Also, as you posted, there are great uses for Wave beyond collaboration that include embedding Waves on websites to super size comments.<br /><a href="http://futuremediachange.com/2009/11/how-news-organizations-are-using-google-wave/" rel="nofollow"></a><a href="http://futuremediachange.com/2009/11/how-news-o.." rel="nofollow">http://futuremediachange.com/2009/11/how-news-o..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amilh</title>
		<link>http://futuremediachange.com/2009/11/google-waves-two-nearly-fatal-flaws/comment-page-1/#comment-84</link>
		<dc:creator>amilh</dc:creator>
		<pubDate>Mon, 30 Nov 2009 18:01:35 +0000</pubDate>
		<guid isPermaLink="false">http://futuremediachange.com/?p=761#comment-84</guid>
		<description>Google didn&#039;t really have many options with what to do with Wave.  They can&#039;t release it as is to the public because a) it&#039;s not ready and b) people wouldn&#039;t know how to use it.  By going Beta they get to test out all the potential problems with Wave and start to tinker before going Rogue, i mean public.  &lt;br&gt;&lt;br&gt;Wave has a few things going for it that most other collaboration tools don&#039;t too.  1) It&#039;s fecking Google, since you&#039;re already one Gmail it&#039;s quite easy to include wave updates.  There is already a firefox plugin that notifies you when you get a wave (mashable.com/2009/10/14/google-wave-notifier/). &lt;br&gt; 2) It replaces most of your other tools.  When wave gets perfected it&#039;s going to eliminate or make redundant a lot of google tools that you&#039;re already using; gchat, docs, etc.  Why use the products separately when you can integrate and real time chat at the same time?&lt;br&gt;&lt;br&gt;3) Apps - when people start developing apps to fix the inherent problems with Wave we&#039;re going to see some pretty snazzy stuff come out that is going to make the tool even more fun and efficnet to sue.&lt;br&gt;&lt;br&gt;wave on.</description>
		<content:encoded><![CDATA[<p>Google didn&#39;t really have many options with what to do with Wave.  They can&#39;t release it as is to the public because a) it&#39;s not ready and b) people wouldn&#39;t know how to use it.  By going Beta they get to test out all the potential problems with Wave and start to tinker before going Rogue, i mean public.  </p>
<p>Wave has a few things going for it that most other collaboration tools don&#39;t too.  1) It&#39;s fecking Google, since you&#39;re already one Gmail it&#39;s quite easy to include wave updates.  There is already a firefox plugin that notifies you when you get a wave (mashable.com/2009/10/14/google-wave-notifier/). <br /> 2) It replaces most of your other tools.  When wave gets perfected it&#39;s going to eliminate or make redundant a lot of google tools that you&#39;re already using; gchat, docs, etc.  Why use the products separately when you can integrate and real time chat at the same time?</p>
<p>3) Apps &#8211; when people start developing apps to fix the inherent problems with Wave we&#39;re going to see some pretty snazzy stuff come out that is going to make the tool even more fun and efficnet to sue.</p>
<p>wave on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
