<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/css" media="screen" href="http://s2.wp.com/wp-content/themes/vip/newyorkobserver/stylesheets/rss.css"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	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>Betabeat &#187; google wave</title>
	<atom:link href="http://betabeat.com/tag/google-wave/feed/" rel="self" type="application/rss+xml" />
	<link>http://betabeat.com</link>
	<description>Just another WordPress.com site</description>
	<lastBuildDate>Wed, 22 May 2013 20:19:47 +0000</lastBuildDate>
	<language></language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='betabeat.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Betabeat &#187; google wave</title>
		<link>http://betabeat.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://betabeat.com/osd.xml" title="Betabeat" />
	<atom:link rel='hub' href='http://betabeat.com/?pushpress=hub'/>
		<item>
				
		<title>Team of Devs So Crushed by Google Wave&#8217;s Shuttering That They Built Their Own Version</title>

		<comments>http://betabeat.com/2012/06/google-wave-rizzoma-06202012/#comments</comments>
		<pubDate>Wed, 20 Jun 2012 11:01:32 -0400</pubDate>
					<link>http://betabeat.com/2012/06/google-wave-rizzoma-06202012/</link>
			<dc:creator>Jessica Roy</dc:creator>
				
		<guid isPermaLink="false">http://betabeat.com/?p=51122</guid>
		<description><![CDATA[<p><div id="attachment_51130" class="wp-caption alignleft" style="width: 310px"><a href="http://blog.rizzoma.com/2012/04/27/work-and-travel-in-ukraine/"><img class="size-medium wp-image-51130" title="Rizzoma" src="http://nyobetabeat.files.wordpress.com/2012/06/komanda500r.png?w=300" alt="" width="300" height="214" /></a><p class="wp-caption-text">The Rizzoma team. (Photo: Rizzoma)</p></div></p>
<p>Remember Google Wave, the collaborative workspace tool pushed by Google a few years back that (like most of the search behemoth's social products) never really got traction? By the last death knell of Wave, Google was so over it that the email they sent out announcing that it would be shut down even <a href="http://betabeat.com/2012/03/google-google-wave-google-wage-misspell-03192012/">misspelled</a> the name of the product as "Google Wage." Yikes.</p>
<p>Despite Wave's lack of appeal as a commercial product, it did have some enthusiastic fans. It was one of those things where you either detested it or wouldn't shut up about it. Admittedly, this reporter forced her entire blog staff in college to employ Wave as a productivity tool, much to the chagrin of the majority of staffers who oddly preferred frenzied Gchat messages and group emails. But it seems like we aren't alone in our passion for Wave--in fact, our love for the product is small potatoes compared to the team at <a href="http://www.rizzoma.com/">Rizzoma</a>, who were literally so depressed by Wave's closure that they moved to the Ukraine for two months to build an alternative.</p>
<p><!--more-->"Our team loved the Wave. We've used it in our business and just for fun conversations. There was no way we could go back to email," wrote Rizzoma UX visioner Daniil Kravtsov in an email to Betabeat. "When Google decided to shut the project down we had only one true way — to resurrect the great idea and continue its development."</p>
<p><em>Hardcore</em>.</p>
<p>From mid-July to September 2011, the Rizzoma team <a href="http://blog.rizzoma.com/2012/04/27/work-and-travel-in-ukraine/">worked</a>, lived and hacked from Odessa, Ukraine on an online collaboration tool that could mirror the functionality of the Google product they missed so much. The result is a stylized real-time collaboration platform that offers many of the same features that Wave did, including real-time editing, polls and full-text search.</p>
<p>Mr. Kravtsov told us that Rizzoma has 3,000 active users and counting. "Will the earthlings treasure the [Wave] idea this time?" he asked. We're not sure, but a Wave clone seemed too amusing to ignore.</p>
]]></description>
		<content:encoded><![CDATA[<p><div id="attachment_51130" class="wp-caption alignleft" style="width: 310px"><a href="http://blog.rizzoma.com/2012/04/27/work-and-travel-in-ukraine/"><img class="size-medium wp-image-51130" title="Rizzoma" src="http://nyobetabeat.files.wordpress.com/2012/06/komanda500r.png?w=300" alt="" width="300" height="214" /></a><p class="wp-caption-text">The Rizzoma team. (Photo: Rizzoma)</p></div></p>
<p>Remember Google Wave, the collaborative workspace tool pushed by Google a few years back that (like most of the search behemoth's social products) never really got traction? By the last death knell of Wave, Google was so over it that the email they sent out announcing that it would be shut down even <a href="http://betabeat.com/2012/03/google-google-wave-google-wage-misspell-03192012/">misspelled</a> the name of the product as "Google Wage." Yikes.</p>
<p>Despite Wave's lack of appeal as a commercial product, it did have some enthusiastic fans. It was one of those things where you either detested it or wouldn't shut up about it. Admittedly, this reporter forced her entire blog staff in college to employ Wave as a productivity tool, much to the chagrin of the majority of staffers who oddly preferred frenzied Gchat messages and group emails. But it seems like we aren't alone in our passion for Wave--in fact, our love for the product is small potatoes compared to the team at <a href="http://www.rizzoma.com/">Rizzoma</a>, who were literally so depressed by Wave's closure that they moved to the Ukraine for two months to build an alternative.</p>
<p><!--more-->"Our team loved the Wave. We've used it in our business and just for fun conversations. There was no way we could go back to email," wrote Rizzoma UX visioner Daniil Kravtsov in an email to Betabeat. "When Google decided to shut the project down we had only one true way — to resurrect the great idea and continue its development."</p>
<p><em>Hardcore</em>.</p>
<p>From mid-July to September 2011, the Rizzoma team <a href="http://blog.rizzoma.com/2012/04/27/work-and-travel-in-ukraine/">worked</a>, lived and hacked from Odessa, Ukraine on an online collaboration tool that could mirror the functionality of the Google product they missed so much. The result is a stylized real-time collaboration platform that offers many of the same features that Wave did, including real-time editing, polls and full-text search.</p>
<p>Mr. Kravtsov told us that Rizzoma has 3,000 active users and counting. "Will the earthlings treasure the [Wave] idea this time?" he asked. We're not sure, but a Wave clone seemed too amusing to ignore.</p>
]]></content:encoded>
		<wfw:commentRss>http://betabeat.com/2012/06/google-wave-rizzoma-06202012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://2.gravatar.com/avatar/b59d8cbbeb9009e27771e8c6863ee21a?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jroyobserver</media:title>
		</media:content>

		<media:content url="http://nyobetabeat.files.wordpress.com/2012/06/komanda500r.png?w=300" medium="image">
			<media:title type="html">Rizzoma</media:title>
		</media:content>
	</item>
		<item>
				
		<title>Google Accidentally Misspells Name of Its Own Product</title>

		<comments>http://betabeat.com/2012/03/google-google-wave-google-wage-misspell-03192012/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 19:06:35 -0400</pubDate>
					<link>http://betabeat.com/2012/03/google-google-wave-google-wage-misspell-03192012/</link>
			<dc:creator>Jessica Roy</dc:creator>
				
		<guid isPermaLink="false">http://www.betabeat.com/?p=34043</guid>
		<description><![CDATA[<p><div id="attachment_34046" class="wp-caption alignleft" style="width: 290px"><a href="http://www.betabeat.com/2012/03/19/google-google-wave-google-wage-misspell-03192012/wage/" rel="attachment wp-att-34046"><img class=" wp-image-34046 " title="wage" src="http://nyobetabeat.files.wordpress.com/2012/03/wage.jpg?w=400&h=208" alt="" width="280" height="146" /></a><p class="wp-caption-text">An email sent from "Google Wage." (twitter.com/alexcornell)</p></div></p>
<p>If you got an email in your inbox today from the Google Wage team, it's not an announcement about a new paycheck tracking tool from the 'Plex. Nor is it a social bet-placing arena, where you can play poker with your friends. Actually, it's just a PR faux pas: Google misspelled the name of its own product.</p>
<p><!--more-->In an email sent to users about the shuttering of Google Wave, the sender name was spelled "Google Wage," an obvious misspelling of "Google Wave." Perhaps Google's PR team was so busy <a href="http://www.betabeat.com/2012/03/15/google-pr-stunt-wsj-the-onion/">pretending</a> old search features are new that they forgot how to spell.</p>
<p>As with most embarrassing events, Twitter users didn't miss a beat: Soon, a <a href="https://twitter.com/#!/search/%23googlewage">hashtag</a> was born.</p>
<p>"Love it when a billion dollar company can't spell their own product name," <a href="https://twitter.com/#!/alexcornell/status/181802335289348097/photo/1">tweeted</a> designer Alex Cornell, along with a screenshot of the offending email.</p>
<p>Some users saw opportunity in Google's mistake. "Dear @google, If you hire me, I promise to never misspell your product names. I'm great at proofing," <a href="https://twitter.com/#!/thechristinecg/status/181858206685990913">said</a> Christine, who goes by @thechristinecg.</p>
<p>It's fair to note that the "V" and "G" keys are adjacent on the keyboard, and everyone makes typos now and then. But perhaps hiring another proofreader isn't such a bad idea afterall.</p>
]]></description>
		<content:encoded><![CDATA[<p><div id="attachment_34046" class="wp-caption alignleft" style="width: 290px"><a href="http://www.betabeat.com/2012/03/19/google-google-wave-google-wage-misspell-03192012/wage/" rel="attachment wp-att-34046"><img class=" wp-image-34046 " title="wage" src="http://nyobetabeat.files.wordpress.com/2012/03/wage.jpg?w=400&h=208" alt="" width="280" height="146" /></a><p class="wp-caption-text">An email sent from "Google Wage." (twitter.com/alexcornell)</p></div></p>
<p>If you got an email in your inbox today from the Google Wage team, it's not an announcement about a new paycheck tracking tool from the 'Plex. Nor is it a social bet-placing arena, where you can play poker with your friends. Actually, it's just a PR faux pas: Google misspelled the name of its own product.</p>
<p><!--more-->In an email sent to users about the shuttering of Google Wave, the sender name was spelled "Google Wage," an obvious misspelling of "Google Wave." Perhaps Google's PR team was so busy <a href="http://www.betabeat.com/2012/03/15/google-pr-stunt-wsj-the-onion/">pretending</a> old search features are new that they forgot how to spell.</p>
<p>As with most embarrassing events, Twitter users didn't miss a beat: Soon, a <a href="https://twitter.com/#!/search/%23googlewage">hashtag</a> was born.</p>
<p>"Love it when a billion dollar company can't spell their own product name," <a href="https://twitter.com/#!/alexcornell/status/181802335289348097/photo/1">tweeted</a> designer Alex Cornell, along with a screenshot of the offending email.</p>
<p>Some users saw opportunity in Google's mistake. "Dear @google, If you hire me, I promise to never misspell your product names. I'm great at proofing," <a href="https://twitter.com/#!/thechristinecg/status/181858206685990913">said</a> Christine, who goes by @thechristinecg.</p>
<p>It's fair to note that the "V" and "G" keys are adjacent on the keyboard, and everyone makes typos now and then. But perhaps hiring another proofreader isn't such a bad idea afterall.</p>
]]></content:encoded>
		<wfw:commentRss>http://betabeat.com/2012/03/google-google-wave-google-wage-misspell-03192012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://2.gravatar.com/avatar/becf95fa833b8aeb13f7720732bd6dc6?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jhanasobserver</media:title>
		</media:content>

		<media:content url="http://nyobetabeat.files.wordpress.com/2012/03/wage.jpg?w=400&#38;h=208" medium="image">
			<media:title type="html">wage</media:title>
		</media:content>
	</item>
		<item>
				
		<title>R.I.P., Google Wave</title>

		<comments>http://betabeat.com/2011/11/r-i-p-google-wave/#comments</comments>
		<pubDate>Wed, 23 Nov 2011 16:29:11 -0400</pubDate>
					<link>http://betabeat.com/2011/11/r-i-p-google-wave/</link>
			<dc:creator>Adrianne Jeffries</dc:creator>
				
		<guid isPermaLink="false">http://www.betabeat.com/?p=22547</guid>
		<description><![CDATA[<p>What Google products are you thankful for this Thanksgiving? We hope you didn't say Google Wave, because we just got the death email from base camp Googleplex. Wave's demise now has a date. Assuming the world survives the new year, all waves will be read-only as of January 31 and the service will give up the ghost at the end of April. The full email, after the jump.<!--more--></p>
<blockquote><p>Dear Wavers,</p>
<p>More than a year ago, we <a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html" target="_blank">announced</a> that Google Wave would no longer be developed as a separate product. At the time, we committed to maintaining the site at least through to the end of 2010. Today, we are sharing the specific dates for ending this maintenance period and shutting down Wave. As of January 31, 2012, all waves will be read-only, and the Wave service will be turned off on April 30, 2012. You will be able to continue exporting individual waves using the existing PDF export feature until the Google Wave service is turned off. We encourage you to export any important data before April 30, 2012.</p>
<p>If you would like to continue using Wave, there are a number of open source projects, including <a href="http://incubator.apache.org/wave/" target="_blank">Apache Wave</a>. There is also an open source project called <a href="http://code.google.com/p/walkaround/" target="_blank">Walkaround</a> that includes an <a href="http://code.google.com/p/walkaround/wiki/ImportingWaves" target="_blank">experimental feature</a> that lets you import all your Waves from Google. This feature will also work until the Wave service is turned off on April 30, 2012.</p>
<p>For more details, please see our <a href="http://www.google.com/support/wave/bin/answer.py?answer=1083134" target="_blank">help center</a>.</p>
<p>Yours sincerely,</p>
<p>The Wave Team</p></blockquote>
<p>&nbsp;</p>
]]></description>
		<content:encoded><![CDATA[<p>What Google products are you thankful for this Thanksgiving? We hope you didn't say Google Wave, because we just got the death email from base camp Googleplex. Wave's demise now has a date. Assuming the world survives the new year, all waves will be read-only as of January 31 and the service will give up the ghost at the end of April. The full email, after the jump.<!--more--></p>
<blockquote><p>Dear Wavers,</p>
<p>More than a year ago, we <a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html" target="_blank">announced</a> that Google Wave would no longer be developed as a separate product. At the time, we committed to maintaining the site at least through to the end of 2010. Today, we are sharing the specific dates for ending this maintenance period and shutting down Wave. As of January 31, 2012, all waves will be read-only, and the Wave service will be turned off on April 30, 2012. You will be able to continue exporting individual waves using the existing PDF export feature until the Google Wave service is turned off. We encourage you to export any important data before April 30, 2012.</p>
<p>If you would like to continue using Wave, there are a number of open source projects, including <a href="http://incubator.apache.org/wave/" target="_blank">Apache Wave</a>. There is also an open source project called <a href="http://code.google.com/p/walkaround/" target="_blank">Walkaround</a> that includes an <a href="http://code.google.com/p/walkaround/wiki/ImportingWaves" target="_blank">experimental feature</a> that lets you import all your Waves from Google. This feature will also work until the Wave service is turned off on April 30, 2012.</p>
<p>For more details, please see our <a href="http://www.google.com/support/wave/bin/answer.py?answer=1083134" target="_blank">help center</a>.</p>
<p>Yours sincerely,</p>
<p>The Wave Team</p></blockquote>
<p>&nbsp;</p>
]]></content:encoded>
		<wfw:commentRss>http://betabeat.com/2011/11/r-i-p-google-wave/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://2.gravatar.com/avatar/becf95fa833b8aeb13f7720732bd6dc6?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">jhanasobserver</media:title>
		</media:content>
	</item>
	</channel>
</rss>
