<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Google Wave: When More Is Too Much</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Mon, 13 Feb 2012 05:01:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: ann michael</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-20228</link>
		<dc:creator><![CDATA[ann michael]]></dc:creator>
		<pubDate>Thu, 05 Aug 2010 14:19:57 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-20228</guid>
		<description><![CDATA[Google Waves goodbye to real-time collaboration tool http://bit.ly/9mhauV 

Fast Company: http://www.fastcompany.com/1677794/google-wave-poorly-understood-and-underused-is-officially-dead?partner=homepage_newsletter

Ironically it was JUST starting to be manageable for me.  But no one gets this kind of time to make a product relevant to an audience - not even Google!]]></description>
		<content:encoded><![CDATA[<p>Google Waves goodbye to real-time collaboration tool <a href="http://bit.ly/9mhauV" rel="nofollow">http://bit.ly/9mhauV</a> </p>
<p>Fast Company: <a href="http://www.fastcompany.com/1677794/google-wave-poorly-understood-and-underused-is-officially-dead?partner=homepage_newsletter" rel="nofollow">http://www.fastcompany.com/1677794/google-wave-poorly-understood-and-underused-is-officially-dead?partner=homepage_newsletter</a></p>
<p>Ironically it was JUST starting to be manageable for me.  But no one gets this kind of time to make a product relevant to an audience &#8211; not even Google!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Technology Reality Check &#8212; The Fable of the Facebook Login &#171; The Scholarly Kitchen</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-7634</link>
		<dc:creator><![CDATA[A Technology Reality Check &#8212; The Fable of the Facebook Login &#171; The Scholarly Kitchen]]></dc:creator>
		<pubDate>Fri, 12 Feb 2010 11:06:45 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-7634</guid>
		<description><![CDATA[[...] technologies here on the Scholarly Kitchen &#8212; new devices, new services, thoughts about often complex tools to create new ways to present information.  And then, something like this comes along, a stark (if [...]]]></description>
		<content:encoded><![CDATA[<p>[...] technologies here on the Scholarly Kitchen &#8212; new devices, new services, thoughts about often complex tools to create new ways to present information.  And then, something like this comes along, a stark (if [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Some Memorable Dishes from the Kitchen in 2009 &#171; The Scholarly Kitchen</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-6184</link>
		<dc:creator><![CDATA[Some Memorable Dishes from the Kitchen in 2009 &#171; The Scholarly Kitchen]]></dc:creator>
		<pubDate>Thu, 24 Dec 2009 10:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-6184</guid>
		<description><![CDATA[[...] Google Wave: When More Is Too Much [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Google Wave: When More Is Too Much [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ann michael</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-5553</link>
		<dc:creator><![CDATA[ann michael]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 15:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-5553</guid>
		<description><![CDATA[Funny - I just read another post on Mashable about the same topic - http://mashable.com/2009/11/08/google-wave-better-than-twitter-conference/

Kristen Ratan had tweeted about it.

Wave definitely seems to have some great possibilities there - much better than the disconnected conversation on Twitter.

Again, having critical mass of people on the platform will determine how long it takes that to catch on.

a]]></description>
		<content:encoded><![CDATA[<p>Funny &#8211; I just read another post on Mashable about the same topic &#8211; <a href="http://mashable.com/2009/11/08/google-wave-better-than-twitter-conference/" rel="nofollow">http://mashable.com/2009/11/08/google-wave-better-than-twitter-conference/</a></p>
<p>Kristen Ratan had tweeted about it.</p>
<p>Wave definitely seems to have some great possibilities there &#8211; much better than the disconnected conversation on Twitter.</p>
<p>Again, having critical mass of people on the platform will determine how long it takes that to catch on.</p>
<p>a</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Roberts</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-5552</link>
		<dc:creator><![CDATA[Philip Roberts]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 15:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-5552</guid>
		<description><![CDATA[I agree that my ambitions for Google Wave workflows are high. However, as pointed out by Charlie Osmond over on http://blog.freshnetworks.com/2009/11/google-wave-vs-twitter-at-conferences/ Google Wave might well offer the best tool for conference commenting and following. It would sure beat adding a hashtag to every message. Inclusion within the conversation (once Wave is freely open) would also be potentially available to a wider audience. 
The built-in ability to poll opinion and to have waves established for each conference track will only enhance the back channel experience of conferences, and potentially if in-Wave video broadcasting becomes achievable, open the conference out to a much larger virtual audience.]]></description>
		<content:encoded><![CDATA[<p>I agree that my ambitions for Google Wave workflows are high. However, as pointed out by Charlie Osmond over on <a href="http://blog.freshnetworks.com/2009/11/google-wave-vs-twitter-at-conferences/" rel="nofollow">http://blog.freshnetworks.com/2009/11/google-wave-vs-twitter-at-conferences/</a> Google Wave might well offer the best tool for conference commenting and following. It would sure beat adding a hashtag to every message. Inclusion within the conversation (once Wave is freely open) would also be potentially available to a wider audience.<br />
The built-in ability to poll opinion and to have waves established for each conference track will only enhance the back channel experience of conferences, and potentially if in-Wave video broadcasting becomes achievable, open the conference out to a much larger virtual audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ann michael</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-5475</link>
		<dc:creator><![CDATA[ann michael]]></dc:creator>
		<pubDate>Thu, 05 Nov 2009 18:12:04 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-5475</guid>
		<description><![CDATA[You are so right about Twitter!  That was another example where I (and many I knew) were very early users - left for a while - and then came back when there was critical mass and we found a compelling reason to participate!]]></description>
		<content:encoded><![CDATA[<p>You are so right about Twitter!  That was another example where I (and many I knew) were very early users &#8211; left for a while &#8211; and then came back when there was critical mass and we found a compelling reason to participate!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Crotty</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-5474</link>
		<dc:creator><![CDATA[David Crotty]]></dc:creator>
		<pubDate>Thu, 05 Nov 2009 17:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-5474</guid>
		<description><![CDATA[I think the really important thing will be what the users decide to do with it, moreso than Google&#039;s announced purpose.  Think in terms of Twitter, which was created as a way of sending out status updates, yet is used for so many other purposes, activities created by the users, not the programmers or planners of the technology.]]></description>
		<content:encoded><![CDATA[<p>I think the really important thing will be what the users decide to do with it, moreso than Google&#8217;s announced purpose.  Think in terms of Twitter, which was created as a way of sending out status updates, yet is used for so many other purposes, activities created by the users, not the programmers or planners of the technology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ann michael</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-5473</link>
		<dc:creator><![CDATA[ann michael]]></dc:creator>
		<pubDate>Thu, 05 Nov 2009 16:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-5473</guid>
		<description><![CDATA[&quot;Don&#039;t judge it based on how it looks today, try to have a little vision and see what it can (will) become.&quot; (from the http://www.jasonkolb.com/ reference)

Just to be clear I am VERY excited about what it can become and I do see some neat uses.  All of the articles you point to underline that it&#039;s moving in a great direction and that it might get to where it needs to be faster than many other apps have in the past.

For me, I&#039;ll wait a bit until the dust settles or until I have a specific use case that I know will benefit by Wave.

That&#039;s all!]]></description>
		<content:encoded><![CDATA[<p>&#8220;Don&#8217;t judge it based on how it looks today, try to have a little vision and see what it can (will) become.&#8221; (from the <a href="http://www.jasonkolb.com/" rel="nofollow">http://www.jasonkolb.com/</a> reference)</p>
<p>Just to be clear I am VERY excited about what it can become and I do see some neat uses.  All of the articles you point to underline that it&#8217;s moving in a great direction and that it might get to where it needs to be faster than many other apps have in the past.</p>
<p>For me, I&#8217;ll wait a bit until the dust settles or until I have a specific use case that I know will benefit by Wave.</p>
<p>That&#8217;s all!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Smith</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-5471</link>
		<dc:creator><![CDATA[David Smith]]></dc:creator>
		<pubDate>Thu, 05 Nov 2009 15:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-5471</guid>
		<description><![CDATA[I think it&#039;s important to distinguish between the client and the protocol when talking about Wave. Wave is built on XMPP which is an open standard - Google&#039;s extensions to this protocol are also open. Note that XMPP powers a number of IM clients...

So although the client that Google has built is the only game in town right now, it most certainly doesn&#039;t have to be. Likewise the fact that hosting a wave server is just around the corner and is an explicit part of the development pathway (Anne - I think you&#039;ll find this very useful). (http://mashable.com/2009/11/02/google-wave-federation/)

Novell have announced Pulse which is a serious attempt to be more enterprise friendly (http://mashable.com/2009/11/04/novell-pulse/) and (http://www.novell.com/media/media.php?media=novell-pulse)

Personally the aspects of Wave that really excite me the most are the gadgets and the robots, some of the scientific ones that are out there point to some really exciting possibilities. Possibilities that could well fundamentally rewrite the rules on what a research paper is for example.

I think you might also find this perspective of interest as well: http://www.jasonkolb.com/ Go read his thoughts on Wave. Might change your viewpoint quite radically.

I&#039;m really excited about the possibilities here. I think that this is a major play by Google. It&#039;s not even a beta yet. If they work on it for 3 years, I wonder if it will have the same impact as twitter is having on the social landscape... As for facebook - I think the ability to exert your own control over your content (via a server you host) pretty much could end facebook as a viable entity if this protocol takes off.]]></description>
		<content:encoded><![CDATA[<p>I think it&#8217;s important to distinguish between the client and the protocol when talking about Wave. Wave is built on XMPP which is an open standard &#8211; Google&#8217;s extensions to this protocol are also open. Note that XMPP powers a number of IM clients&#8230;</p>
<p>So although the client that Google has built is the only game in town right now, it most certainly doesn&#8217;t have to be. Likewise the fact that hosting a wave server is just around the corner and is an explicit part of the development pathway (Anne &#8211; I think you&#8217;ll find this very useful). (<a href="http://mashable.com/2009/11/02/google-wave-federation/" rel="nofollow">http://mashable.com/2009/11/02/google-wave-federation/</a>)</p>
<p>Novell have announced Pulse which is a serious attempt to be more enterprise friendly (<a href="http://mashable.com/2009/11/04/novell-pulse/" rel="nofollow">http://mashable.com/2009/11/04/novell-pulse/</a>) and (<a href="http://www.novell.com/media/media.php?media=novell-pulse" rel="nofollow">http://www.novell.com/media/media.php?media=novell-pulse</a>)</p>
<p>Personally the aspects of Wave that really excite me the most are the gadgets and the robots, some of the scientific ones that are out there point to some really exciting possibilities. Possibilities that could well fundamentally rewrite the rules on what a research paper is for example.</p>
<p>I think you might also find this perspective of interest as well: <a href="http://www.jasonkolb.com/" rel="nofollow">http://www.jasonkolb.com/</a> Go read his thoughts on Wave. Might change your viewpoint quite radically.</p>
<p>I&#8217;m really excited about the possibilities here. I think that this is a major play by Google. It&#8217;s not even a beta yet. If they work on it for 3 years, I wonder if it will have the same impact as twitter is having on the social landscape&#8230; As for facebook &#8211; I think the ability to exert your own control over your content (via a server you host) pretty much could end facebook as a viable entity if this protocol takes off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Roberts</title>
		<link>http://scholarlykitchen.sspnet.org/2009/10/30/google-wave-when-more-is-too-much/#comment-5429</link>
		<dc:creator><![CDATA[Philip Roberts]]></dc:creator>
		<pubDate>Tue, 03 Nov 2009 12:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6731#comment-5429</guid>
		<description><![CDATA[This morning on Life Hacker there was a very useful link to &quot;The Complete Wave Guide&quot; (wiki book)  http://completewaveguide.com/ open access resource.]]></description>
		<content:encoded><![CDATA[<p>This morning on Life Hacker there was a very useful link to &#8220;The Complete Wave Guide&#8221; (wiki book)  <a href="http://completewaveguide.com/" rel="nofollow">http://completewaveguide.com/</a> open access resource.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

