<?xml version="1.0" encoding="UTF-8"?>
<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/"
	>

<channel>
	<title>The Geekorium &#187; debate</title>
	<atom:link href="http://the.geekorium.com/tag/debate/feed/" rel="self" type="application/rss+xml" />
	<link>http://the.geekorium.com</link>
	<description>Home of Rex Havoc, Space Adventurer and other assorted Geekeries.</description>
	<lastBuildDate>Fri, 18 May 2012 09:30:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>Get Your Wave Peeves Off Your Chest!</title>
		<link>http://the.geekorium.com/get-your-wave-peeves-off-your-chest/</link>
		<comments>http://the.geekorium.com/get-your-wave-peeves-off-your-chest/#comments</comments>
		<pubDate>Mon, 26 Apr 2010 02:00:48 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[community]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[discussion]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477719</guid>
		<description><![CDATA[I'd like to hear what things you'd change about wave if you could.<p><a href="http://the.geekorium.com/get-your-wave-peeves-off-your-chest/">Get Your Wave Peeves Off Your Chest!</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Something that’s been bugging me about the Google Wave interface are the icons that show you three participants from each wave in your inbox (and other searches). The origins of the feature make sense — in email we’re used to seeing who an email is <strong>from</strong> right from our inbox. In one and two person waves it does kind of make sense, but when you have multiple participants the icons stop being useful and just become clutter. To me it adds nothing to my ability to identify a wave and just makes my inbox “noisy”. The icons <em>in</em> the wave make sense, but I’d like a more thought out approach to identifying waves. Something like:</p>


<ul>
<li>Make waves I’ve started a slightly different colour (like sites where the author’s comments are shaded slightly blue).</li>
<li>Don’t show icons at all in the inbox/searches (or make it easy to show and hide).</li>
<li>Let me tag or bookmark specific blips within waves and make it obvious from the inbox which waves have “starred blips”.</li>
</ul>



<p>Now this post wasn’t started just as a gripe against something I’d like to see changed — I’d like to hear what things you’d change about wave if you could. I’m not necessarily talking features we know might come (like the <a href="http://firstwaves.org/remove-remove-yourself-remove-others/">recently switched on</a> “Remove” button). I mean interface and behaviour changes that don’t make sense to you, or made sense at first, but don’t now you’ve used it a bit. What are your specific gripes and revolutionary ideas that would make using Wave more of a delight for you?</p>

<p><span id="more-229477719"></span></p>

<p>Wave is constantly in a state of flux, so there’s every chance the feature you hate might be altered in future. So get your pet peeves out here in the comments or on <a href="https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BPia29cqgA">this post’s sister wave</a> (embedded)</p>

<p>[wave id=“googlewave.com!w%252BPia29cqgA”] </p><p><a href="http://the.geekorium.com/get-your-wave-peeves-off-your-chest/">Get Your Wave Peeves Off Your Chest!</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/get-your-wave-peeves-off-your-chest/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>8 Google Wave Competitors</title>
		<link>http://the.geekorium.com/8-google-wave-competitors/</link>
		<comments>http://the.geekorium.com/8-google-wave-competitors/#comments</comments>
		<pubDate>Tue, 13 Apr 2010 16:30:54 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[opinion]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477557</guid>
		<description><![CDATA[Google Wave is a product that's trying to do something massive to the way we communicate online. Its stated goal is to be what email might look like if it were invented today. A number of other services have been labeled as competitors to Google Wave, including the recently updated Google Docs (which is too new for me to comment on in this article), but I wanted to take a look at which of these services are *real* competition. Below are the services who show the most promise at becoming the next generation of online communication.<p><a href="http://the.geekorium.com/8-google-wave-competitors/">8 Google Wave Competitors</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.flickr.com/photos/jwthegreat/3951502557/"><img src="http://farm4.static.flickr.com/3445/3951502557_bb869d3375.jpg" alt="" height="375" width="500" /></a></p>

<p>Google Wave is a product that’s trying to do something massive to the way we communicate online. Its stated goal is to be what email might look like if it were invented today. A number of other services are labeled as competitors to Google Wave, including the recently updated Google Docs (which is too new for me to comment on in this article), but I wanted to take a look at which of these services are <strong>real</strong> competition. Below are the services who show the most promise at becoming the next generation of online communication.</p>

<h3>Microsoft Sharepoint</h3>

<p>Microsoft Sharepoint is a suite of content management tools to maintain and collaborate on documents. While it was never sold as a replacement to email, it was held up as one of the products Google Wave was meant to compete against. But as Steve Gaitten of Bamboo Nation <a href="http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2009/06/04/goolge-wave-vs-sharepoint.aspx">points out</a>, Wave competes with Outlook, not Sharepoint.</p>

<p>It might be possible for Microsoft to transform Outlook in some significant way that expands it beyond email into some sort of super email client. It might even integrate it into Sharepoint a lot further. The truth is, email is Google Wave’s biggest competition. It might be <a href="/why-email-needs-replacing-or-why-wave-matters/">outdated and rough</a>, but it’s the most popular form of communication on the internet. If anything stands a chance at beating Wave, it’s the service that Wave is trying to beat. If email innovation can keep up with user demand, it might just remain the top dog for another 40 years. If Outlook can maintain the large slice of the pie it  has, while innovating on top of email it could still be competing into the future.</p>

<h3>Novell Pulse</h3>

<p>This is exactly the kind of “competition” Google was hoping for when they built Wave. As I’ve said before, Wave’s only hope of replacing email is federation. Only by giving users the choice of Wave provider will users find one that works for them. Novell Pulse might even become a more loved Wave client, and I think that would actually make Google happy. Personally, I’m eagerly awaiting a Pulse preview account.</p>

<h3><a href="http://www.sapstreamwork.com/"><span class="caps">SAP</span> Streamwork</a></h3>

<p>This tool was touted as <a href="http://www.readwriteweb.com/enterprise/2009/12/sap-getting-ready-to-launch-go.php">a Google Wave competitor</a> while in Beta (with the code name 12Sprints or Constellation).</p>

<p>The tool turns out to be a collaboration space for making decisions. It’s not a complete replacement for email, but I’m not sure that was ever their intention. Streamwork allows a team to collaborate and add gadgets to enhance the process.</p>

<blockquote><p>“It was clear we needed to work together,” Meyer said. “We’re excited about what they’re doing, they’re excited about what we’re doing.” Users will be able to share content between the two platforms, he said.</p></blockquote>

<p><cite><a href="http://www.computerworld.com/s/article/9141622/SAP_readying_potential_Google_Wave_rival?taxonomyId=18&amp;pageNumber=2">David Meyer, reported by Computer World</a></cite></p>

<p>It will be interesting to see what sort of integration they build into it.</p>

<h3><a href="http://www.zenbe.com/shareflow">Shareflow</a> and <a href="http://www.tokbox.com/">Toqbox</a></h3>

<p>Much like Streamwork, these tools are not marketed as email replacements, but were <a href="http://www.readwriteweb.com/enterprise/2009/07/shareflow-its-google-wave-but-available-now.php">both</a> <a href="http://www.makeuseof.com/tag/tokbox-etherpad-potential-google-wave-competitors-available-now/">touted</a> as Google Wave competitors.  What they do is allow users to collaborate on documents in real-time. If these sorts of services were better integrated into email (perhaps using GMail’s new oAuth tools) they might be more likely candidates. Otherwise they are really only competing with <a href="http://docs.google.com/">Google Docs</a> and others of that kind.</p>

<h3><a href="http://www.ccbetty.com/">ccBetty</a>, <a href="https://www.syphir.com/">Syphir</a>, <a href="https://etacts.com/">Etacts</a>, <a href="http://www.xobni.com/">Xobni</a>, <a href="http://rapportive.com/">Rapportive</a> et al.</h3>

<p>Products such as ccBetty and the others mentioned <em>enhance</em> email. They exist to remove the holes in email by providing additional information, embedded media, faster searching, or simplified discussion. Some work on GMail, others on Outlook, others work outside any email service by CC-ing a special address onto each email you wish to turn into a discussion. The problem with <strong>all</strong> of these tools as competition for Wave is that the email protocol just doesn’t take these sorts of tools into consideration, so they’re limited by how many services the developers can write for. That is, each service might support Outlook or GMail, but not all the other smaller players in the marketplace. Where Google Wave has this model beat is by including extension support from day one, allowing developers to enhance Wave in whatever ways they can imagine. Any service that federates with Google Wave will also support these extensions, making it a truly open, extensible experience.</p>

<h3><del>EtherPad</del></h3>

<p>This collaboration tool gets its own special crossed out spot because it was one of the strongest, simplest competitors in the collaboration space, but was bought by Google! The developers have obviously since been put to work on Google Docs, as evidenced by the announcement of the <a href="http://googleblog.blogspot.com/2010/04/next-generation-of-google-docs.html">recent update</a>.</p>

<h3>Facebook.</h3>

<p>This one scares me a little. In some ways, Google Wave is the anti-Facebook. Where Wave is built on open technology, uses an open protocol and federates with other services, Facebook is a “walled garden” and keeps users inside their service. Both systems let developers make extensions and apps that use the platform, and Facebook seems to be slowly inching towards including some of the collaboration features that have been missing so far. Facebook has a huge user base, and could easily become some sort of defacto go-to communication platform for the masses. Currently though there are no obvious moves to open up the platform further, making it unlikely to catch on in business, where email still rules.</p>

<h3>Twitter (+ Buzz and other Social Public Messaging)</h3>

<p>Currently, none of the services in their current form pose a threat to email — they’re too limited with their 140 character limits and lack of in-line collaboration. But Twitter (or a more open version of it at least) is the product I think has the most real chance of beating Google Wave at becoming the communication platform of the future.</p>

<p>A distributed network (integrated with Twitter of course) that updates in real-time, with an <span class="caps">API </span>could have many people needing their email less and less. Once you can get updates from your favourite companies and all your friends are on the service, why would you need it? Throw in an extension or two, enhanced private messaging, and you have a very compelling product that could steal users away from email. The platform is so new, no one really knows where it could go in the future, and I suspect it will give Google Wave <strong>and</strong> traditional email a run for their money. It could be Twitter, or Buzz, Status.Net or a new player we’ve never heard of, but the idea has the strongest traction of any I’ve seen.</p>

<h3>Something completely new</h3>

<p>So those are my thoughts about Google Wave’s <em>true</em> competition. Of course, a company could come out of the blue with a product so completely new and exciting it amasses a huge audience that completely abandons email. This is the least likely of all I think, as I’ve stated before I think Wave is our best chance at replacing email wholesale. Alternatively, email will be killed by slow changes to the next generation of social communication. The chances of it happening are dependant on the whims of companies who are trying to make a buck, not replace email so I’m not holding my breath. Email will be replaced by something federated, open, extensible and easy to use. I’ve taken my best shot at predicting what it could be.</p>

<p>What are your thoughts? Is Google Wave our best hope, or is there something even more obvious that could take email’s place?</p>

<p>Image by <a href="http://www.flickr.com/photos/jwthegreat/"><span class="caps">JEFFREY’S MURALS</span></a></p><p><a href="http://the.geekorium.com/8-google-wave-competitors/">8 Google Wave Competitors</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/8-google-wave-competitors/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Wave on Slow Cook</title>
		<link>http://the.geekorium.com/wave-on-slow-cook/</link>
		<comments>http://the.geekorium.com/wave-on-slow-cook/#comments</comments>
		<pubDate>Tue, 16 Mar 2010 12:10:43 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[discussion]]></category>
		<category><![CDATA[future]]></category>
		<category><![CDATA[use case]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477507</guid>
		<description><![CDATA[Google Wave will only succeed (over time) if they have a large collection of useful add ons and competing alternative services that interoperate. They are attempting to replace email in the long term, not replace Twitter in the short term.<p><a href="http://the.geekorium.com/wave-on-slow-cook/">Wave on Slow Cook</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<p>I get the feeling talking to regular web-folk that Google Wave was a huge disappointment for them. With the introduction of Buzz, <a href="http://www.marketingpilgrim.com/2010/02/google-buzz-launches-150-million-user-social-network.html#comment-109554">comments</a> and <a href="http://webworkerdaily.com/2010/02/11/google-buzz-already-better-than-google-wave-and-maybe-facebook-too/">posts</a> <a href="http://blogs.laweekly.com/stylecouncil/tech/is-google-buzz-worth-all-the-b/">flew</a> asking “will this be better than that Google Wave failure?”</p>

<p><a href="http://www.flickr.com/photos/geishabot/4312748848/"><img src="http://farm5.static.flickr.com/4002/4312748848_c00784dd3f.jpg" alt="crock pot" /></a></p>

<p>It’s taken me this long to figure out that people are not viewing Google Wave the way I do. The current technology life cycle goes something like this:</p>

<ol>
	<li>Readers are on the lookout for new products to try, and better yet — beta invites to get early exclusive access to the next big thing.</li>
	<li>They try the site, decide if it fits in with their day-to-day activities and if it gives them any benefit over the last shiny new thing they tried.</li>
	<li>They talk it up to their friends to get them to join, as these sites are almost always no fun without a large number of people you know and respect.</li>
</ol>
Then the cycle repeats for all manner of sites and services.

<p>I do this. Every day I pop open <a href="http://techcrunch.com">Techcrunch</a>, <a href="http://gigaom.com">GigaOm</a>, <a href="http://www.readwriteweb.com/">ReadWriteWeb</a>, <a href="http://webworkerdaily.com/">Web Worker Daily</a> and others to keep informed of the latest hot places I can claim my name on. I’ve joined <a href="http://twitter.com/joshnunn">Twitter</a>, <a href="http://www.facebook.com/joshnunn">Facebook</a>, <a href="http://friendfeed.com/joshnunn">Friendfeed</a>, <a href="http://www.plurk.com/joshnunn">Plurk</a>, and others too numerous to mention all vying to be the place I share my daily activities. It’s almost addictive to keep on top of the latest sites.</p>

<p><span id="more-229477507"></span></p>

<p>I’m guessing a lot of the people who were itching for Wave invites were, like I normally would be, expecting Google Wave to deliver something to replace Facebook or Twitter or Google Docs, or whatever they got in their heads it would be amazing for. It’s unsurprising that people want to use the best tools they can for their work (and leisure). The problem was that Google Wave was never meant to be a replacement for any of these things. It wasn’t even meant to be a replacement for email — not just yet anyway.</p>

<p>The best post about this topic came from Daniel Tenner. <a href="http://danieltenner.com/posts/0012-google-wave.html"><em>What problems does Google Wave solve?</em></a> came out soon after Wave debuted and attempted to explain this disconnect between what people were expecting and what was actually delivered. It’s an excellent read, and vital to the understanding of what Google Wave is meant to be. The short version is: Google is building something that might be our preferred platform for communication some time in the future. They’re not expecting it to be an overnight sensation, they just want people to be aware of it, and start thinking how they can use it to phase out busted email technology.</p>

At the recent <span class="caps">SXSW </span>conference, Louis Gray reported on talks by the GMail team:<br />
<blockquote>Google Wave, which debuted in early beta last year, is a “leapfrog project”, which goes beyond today’s environment, but is set to impact a future Web. </blockquote> <cite><a href="http://blog.louisgray.com/2010/03/gmail-failures-crazy-ideas-and-waves.html">Gmail Failures, Crazy Ideas and Wave’s Leapfrog.</a></cite>

<p>The important thing to keep in your mind here is that Google Wave will only succeed (over time) if they have a large collection of useful add ons and competing alternative services that interoperate. They’re attempting to oust a 30-year-old technology that has morphed and grown and matured and become one of the vital technologies of the web today. Everyone uses it, and it’s been shoehorned into all sorts of roles it’s unsuited for. Google knows that replacing it will not be easy, and they don’t expect it will happen quickly. They do know it will take a lot of work from 3rd party developers to give it even a fraction of the rich ecosystem that email has. So they want to get it right.</p>

<p>So next time you log in to Wave keep that in mind. And if you’re a developer, give it another shot. You’re our best hope of retiring email from our lives and giving us real, exciting and useful new technology as the most ubiquitous communication tool we have.</p>

<p>Image by <span xmlns:cc="http://creativecommons.org/ns#" about="http://www.flickr.com/photos/geishabot/4312748848/"><a rel="cc:attributionURL" href="http://www.flickr.com/photos/geishabot/">http://www.flickr.com/photos/geishabot/</a> / <a rel="license" href="http://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a></span></p><p><a href="http://the.geekorium.com/wave-on-slow-cook/">Wave on Slow Cook</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/wave-on-slow-cook/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>The problems Wave solves</title>
		<link>http://the.geekorium.com/i-believe-that-people-who-dont-see-what-google-wave-is-for-are-simply-looking-at-it-from-the-wrong-angle-wave-is-not-a-social-tool-its-not-twitter-its-not-gtalk-its-not-facebook-it-was-never-designed/</link>
		<comments>http://the.geekorium.com/i-believe-that-people-who-dont-see-what-google-wave-is-for-are-simply-looking-at-it-from-the-wrong-angle-wave-is-not-a-social-tool-its-not-twitter-its-not-gtalk-its-not-facebook-it-was-never-designed/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 00:35:15 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[use case]]></category>

		<guid isPermaLink="false">http://firstwaves.org/post/214211798</guid>
		<description><![CDATA["Wave is built for the corporate environment. It’s a tool for getting work done. And as far as those go, it’s an excellent tool, even at this very early stage."<p><a href="http://the.geekorium.com/i-believe-that-people-who-dont-see-what-google-wave-is-for-are-simply-looking-at-it-from-the-wrong-angle-wave-is-not-a-social-tool-its-not-twitter-its-not-gtalk-its-not-facebook-it-was-never-designed/">The problems Wave solves</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<blockquote></blockquote>
<cite><a href="http://danieltenner.com/posts/0012-google-wave.html">danieltenner.com — What problems does Google WaveÂ solve?</a></cite><p><a href="http://the.geekorium.com/i-believe-that-people-who-dont-see-what-google-wave-is-for-are-simply-looking-at-it-from-the-wrong-angle-wave-is-not-a-social-tool-its-not-twitter-its-not-gtalk-its-not-facebook-it-was-never-designed/">The problems Wave solves</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/i-believe-that-people-who-dont-see-what-google-wave-is-for-are-simply-looking-at-it-from-the-wrong-angle-wave-is-not-a-social-tool-its-not-twitter-its-not-gtalk-its-not-facebook-it-was-never-designed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wave and Real Time Collaboration</title>
		<link>http://the.geekorium.com/wave-and-real-time-collaboration/</link>
		<comments>http://the.geekorium.com/wave-and-real-time-collaboration/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 11:29:47 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[use case]]></category>

		<guid isPermaLink="false">http://firstwaves.org/post/207481173</guid>
		<description><![CDATA["The beauty of it is, the user can control the experience and dictate its purpose."<p><a href="http://the.geekorium.com/wave-and-real-time-collaboration/">Wave and Real Time Collaboration</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<blockquote>This in no way represents a new social networking tool, and I think using it as such would be rather cumbersome. The beauty of it is, the user can control the experience and dictate its purpose.</blockquote>

<p><cite><a href="http://www.michaelfruchter.com/blog/2009/10/google-wave-is-the-future-of-real-time-collaboration/">Google Wave Is The Future of Real Time Collaboration</a></cite></p><p><a href="http://the.geekorium.com/wave-and-real-time-collaboration/">Wave and Real Time Collaboration</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/wave-and-real-time-collaboration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Freedom Problem</title>
		<link>http://the.geekorium.com/the-freedom-problem/</link>
		<comments>http://the.geekorium.com/the-freedom-problem/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 09:12:58 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[users]]></category>

		<guid isPermaLink="false">http://firstwaves.org/post/207428175</guid>
		<description><![CDATA[All of this freedom - being able to add to, edit, or delete anyone else’s blip in any wave - doesn’t just lead to accidental destruction but concerns about people “putting words into their mouths”, and raises a number of trust issues for many.<p><a href="http://the.geekorium.com/the-freedom-problem/">The Freedom Problem</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<blockquote></blockquote> <cite><a href="http://blog.tarynhicks.com.au/early-thoughts-on-google-wave/">Early thoughts on Google Wave</a></cite>

<p>I’m certain that this will not be as big an issue in later iterations of Wave, and there are already some safeguards in place. Nevertheless, it is a real issue to watch as Wave matures.</p><p><a href="http://the.geekorium.com/the-freedom-problem/">The Freedom Problem</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/the-freedom-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What You’re Missing About Google Wave</title>
		<link>http://the.geekorium.com/what-is-amazing-is-that-google-has-developed-a-real-time-communication-framework-that-can-work-in-a-federated-environmentpeople-arent-getting-it-right-now-because-theyre-expecting-the-beta-to-all-be-a/</link>
		<comments>http://the.geekorium.com/what-is-amazing-is-that-google-has-developed-a-real-time-communication-framework-that-can-work-in-a-federated-environmentpeople-arent-getting-it-right-now-because-theyre-expecting-the-beta-to-all-be-a/#comments</comments>
		<pubDate>Sat, 03 Oct 2009 08:36:10 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[users]]></category>

		<guid isPermaLink="false">http://firstwaves.org/post/203242773</guid>
		<description><![CDATA["What is amazing is that Google has developed a real-time communication framework that can work in a federated environment."<p><a href="http://the.geekorium.com/what-is-amazing-is-that-google-has-developed-a-real-time-communication-framework-that-can-work-in-a-federated-environmentpeople-arent-getting-it-right-now-because-theyre-expecting-the-beta-to-all-be-a/">What You’re Missing About Google Wave</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<blockquote></blockquote>

<p><cite><a href="http://macrolinz.com/macrolinz/index.php/2009/10/01/the-point-youre-missing-about-google-wave/"></a></cite></p><p><a href="http://the.geekorium.com/what-is-amazing-is-that-google-has-developed-a-real-time-communication-framework-that-can-work-in-a-federated-environmentpeople-arent-getting-it-right-now-because-theyre-expecting-the-beta-to-all-be-a/">What You’re Missing About Google Wave</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/what-is-amazing-is-that-google-has-developed-a-real-time-communication-framework-that-can-work-in-a-federated-environmentpeople-arent-getting-it-right-now-because-theyre-expecting-the-beta-to-all-be-a/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Implications of Google Wave</title>
		<link>http://the.geekorium.com/implications-of-google-wave/</link>
		<comments>http://the.geekorium.com/implications-of-google-wave/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 12:24:23 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Link]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[use case]]></category>
		<category><![CDATA[users]]></category>

		<guid isPermaLink="false">http://firstwaves.org/post/126417134</guid>
		<description><![CDATA[A recap of the exciting implications of Google Wave for businesses and individuals.<p><a href="http://the.geekorium.com/implications-of-google-wave/">Implications of Google Wave</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<p>A recap of the exciting implications of Google Wave for businesses and individuals.</p>

<p><a href="http://carsonified.com/blog/dev/six-ways-that-google-wave-is-going-to-change-your-business-career-and-life/">Six Ways that Google Wave is Going to Change Your Business, Career and Life [Think Vitamin]</a></p><p><a href="http://the.geekorium.com/implications-of-google-wave/">Implications of Google Wave</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/implications-of-google-wave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wave is Game Changing</title>
		<link>http://the.geekorium.com/wave-is-game-changing/</link>
		<comments>http://the.geekorium.com/wave-is-game-changing/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 12:09:13 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Link]]></category>
		<category><![CDATA[debate]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[use case]]></category>

		<guid isPermaLink="false">http://firstwaves.org/post/126412795</guid>
		<description><![CDATA[A quick overview of the most mind-blowing features of Google Wave.<p><a href="http://the.geekorium.com/wave-is-game-changing/">Wave is Game Changing</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<p>A quick overview of the most mind-blowing features of Google Wave.</p>

<p><a href="http://mashable.com/2009/05/31/google-wave-features/">The Top 6 Game-Changing Features of Google Wave [Mashable]</a></p><p><a href="http://the.geekorium.com/wave-is-game-changing/">Wave is Game Changing</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/wave-is-game-changing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Re-Invention of Email</title>
		<link>http://the.geekorium.com/the-re-invention-of-email/</link>
		<comments>http://the.geekorium.com/the-re-invention-of-email/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 12:04:44 +0000</pubDate>
		<dc:creator>screenbeard</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[Competition]]></category>
		<category><![CDATA[debate]]></category>

		<guid isPermaLink="false">http://firstwaves.org/post/126411581</guid>
		<description><![CDATA[Are tools like <a href="http://www.ccbetty.com/">CC Betty</a> approaching the re-invention of email in a more practical way?<p><a href="http://the.geekorium.com/the-re-invention-of-email/">The Re-Invention of Email</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></description>
			<content:encoded><![CDATA[<blockquote>Can a small startup — made up the two co-founders and one employee working in a studio apartment in Silicon Valley — go head-to-head with a powerhouse like Google on something as revolutionary as the re-invention of e-mail?</blockquote>

<p><cite><a href="http://blogs.zdnet.com/BTL/?p=19215">Can a startup challenge Google on the re-invention of e-mail?</a></cite></p>

<p>Are tools like <a href="http://www.ccbetty.com/">CC Betty</a> approaching the re-invention of email in a more practical way?</p><p><a href="http://the.geekorium.com/the-re-invention-of-email/">The Re-Invention of Email</a> is a post from: <a href="http://the.geekorium.com">The Geekorium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://the.geekorium.com/the-re-invention-of-email/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

