<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>First Waves</title>
	
	<link>http://firstwaves.org</link>
	<description>Examining Google+ as it Grows</description>
	<lastBuildDate>Wed, 13 Jul 2011 13:18:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<cloud domain="firstwaves.org" port="80" path="/?rsscloud=notify" registerProcedure="" protocol="http-post" />
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/firstwaves" /><feedburner:info uri="firstwaves" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://superfeedr.com/hubbub" /><feedburner:emailServiceId>firstwaves</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Google+ (or Google Plus if you wanna be search-engine friendly)</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/p4U4rWiDIBc/</link>
		<comments>http://firstwaves.org/google-plus/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 13:02:33 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[buzz]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[google+]]></category>
		<category><![CDATA[new]]></category>
		<category><![CDATA[sharing]]></category>
		<category><![CDATA[social]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477777</guid>
		<description><![CDATA[So I’m hanging out on Google+. I mean literally of course – the second1 new social network that Google has launched in the last couple of years has a “hangout” feature where you can chat with lots of friends simultaneously via video. I’ve never tried it, so I’m sitting here in the hopes that someone [...]<p><a href="http://firstwaves.org/google-plus/">Google+ (or Google Plus if you wanna be search-engine friendly)</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<p>So I’m hanging out on Google+. I mean literally of course – the second<sup><a href="http://firstwaves.org/google-plus/#footnote_0_229477777" id="identifier_0_229477777" class="footnote-link footnote-identifier-link" title="or third?">1</a></sup> new social network that Google has launched in the last couple of years has a “hangout” feature where you can chat with lots of friends simultaneously via video. I’ve never tried it, so I’m sitting here in the hopes that someone will join in with me. No one has come past yet, but I think that says more about Australian/American time difference and my own social ineptness than the popularity of the feature. I hear very good things about it.</p>

<p>This article isn’t about that feature specifically. This is about Google+ in general. The new social network that <strong>totally</strong> isn’t trying to out-social Facebook<sup><a href="http://firstwaves.org/google-plus/#footnote_1_229477777" id="identifier_1_229477777" class="footnote-link footnote-identifier-link" title="But is really &amp;#8211; everybody knows, you guys">2</a></sup>. It seems quite a hit! But then so was Buzz initially. You remember Buzz? The social network built knee-deep into GMail that a lot of people tried, but no one really liked<sup><a href="http://firstwaves.org/google-plus/#footnote_2_229477777" id="identifier_2_229477777" class="footnote-link footnote-identifier-link" title="not really deep down">3</a></sup>. There was also Wave – but that never made sense to most people<sup><a href="http://firstwaves.org/google-plus/#footnote_3_229477777" id="identifier_3_229477777" class="footnote-link footnote-identifier-link" title="although I never knew why &amp;#8211; it was pretty straight forward">4</a></sup>. I mock, but only out of love. Google, despite their failures are not a company to give up on something once they have it in their sights, and understandably they want to get in on this “social” act.</p>

<p><a href="http://xkcd.com/918/"><img alt="" src="http://imgs.xkcd.com/comics/googleplus.png" title="Google+ xkcd" class="alignnone" width="535" height="281" /></a></p>

<p>What “social” means exactly is anyone’s guess, but in vague terms it means somehow putting all that information you generate when you browse the web and share the cool stuff you find with your friends to use. Sites like Facebook are all about giving you a central place to post videos and photos you like so other people can see how witty and clever you are for liking Transformers before they were ruined<sup><a href="http://firstwaves.org/google-plus/#footnote_4_229477777" id="identifier_4_229477777" class="footnote-link footnote-identifier-link" title="or exploded">5</a></sup> by Michael Bay. This sort of sharing has come a long way since the web was made. It used to be that you had to own your own website and manually copy/paste links and videos into your pages and hope to hell that people might find, and occasionally re-visit, your site. Then sites like Blogger and WordPress came along and made that somewhat easier, then Tumblr and Facebook – making those sorts of short and snappy link sharing posts easier and easier to do. Now you wave your mouse in the direction of the Facebook tab and it pulls out that it’s a Youtube video and picks out the title and description and even embeds the video, and you barely have to do <strong>anything</strong>. Well now Google is heading one step further. They aren’t there right now – Google+ is still a lot like Facebook on the surface – but deeper down the steps are there to become something massive.</p>

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

<p>Google+ is a service where you share your links, photos and videos with people in your “Circles”. You group the people you know into named Circles to make sharing easier and less prone to accidents of the “sharing photos of myself drunk with Aunt Sally” variety. For example, you create a “Work” circle, a “Family” circle and potentially a “Drunk shenanigans” circle. Then each time you post a picture or a report, you can easily assign it to be seen by the appropriate group. For the record: Facebook offers a similar option, but <strong>I’ve</strong> rarely used it, and I can’t imagine my mum has ever bothered.</p>

<p>Then there’s the Hangout feature I’ve mentioned above. When you’re online, you can set up your webcam for chats with whichever friends happen to be browsing Google+ at the time.</p>

<p>The third major feature at launch is “Sparks” – a kind of automatic interesting article finder. Type in a few keywords about what you’re interested in, and you get your stream filled with articles that match those keywords. I find this feature somewhat limited at the moment. A few of the articles it’s uncovered have been interesting, but mostly it’s just more of the same sort of thing I can get at one or more of a dozen similar services. Once it’s fully integrated into everyone’s Google account though – like my mum’s – I can imagine it being useful for some people to find new and interesting articles they might otherwise not go searching for.</p>

<p>Thus we get to the crux of the matter: integration. Google practically runs the web right now, despite the valiant efforts of Microsoft and up-and-comers like Duck Duck Go, and despite the sneak-in-from-behind services like Twitter and Facebook. If you want an answer to something you most likely start at Google and work your way from there. But Google recognise it’s only a matter of time before someone takes that “social” power that other sites like Twitter and Facebook have and turn it into a more useful information finding service. The power of social is to hopefully take it one step further and start recommending things to you before you even recognise you were looking for it. To help you dig out more reliable information – reliable because a friend or relative has already used it and shared about it<sup><a href="http://firstwaves.org/google-plus/#footnote_5_229477777" id="identifier_5_229477777" class="footnote-link footnote-identifier-link" title="It&amp;#8217;s also to make advertising more profitable, but that&amp;#8217;s another story">6</a></sup>. Google is the biggest search engine on the planet and has been for years. On top of that, Google has sites like Blogger (for web pages) and Picasa (for photos) and – because you might not have actually heard of those – Youtube for video.</p>

<p>Google’s plan with Google+ has already started. You can “Plus One” any search result to indicate to other people in your networks that a particular website is a good result – similar to Facebook’s “Like” button, but on your search page. Now website owners can embed these buttons onto their sites, and you can “Plus One” after you’ve visited – the results are shown to your friends in <strong>their</strong> Google searches.</p>

<p>The next step will be to turn this functionality on on Youtube and their other properties. When you “Like” a video – soon to become “+1″ no doubt – this will be added to your list of +1s on your profile and I’m imagining eventually integrated into your stream. As more and more Google properties are built onto the Google Plus platform, stuff you have found useful or beautiful or interesting will be offered to your friends and family as reliable content that they might also find useful or beautiful or interesting. It’s all part of Google’s plan to find ways to understand what you do on the web and make themselves more useful so you use them more<sup><a href="http://firstwaves.org/google-plus/#footnote_6_229477777" id="identifier_6_229477777" class="footnote-link footnote-identifier-link" title="and see and click on more ads">7</a></sup>. It’s a grand vision. It’s easy to imagine this as the start of something big, which is why I’m so excited about it.</p>

<p><a href="http://firstwaves.org/google-plus/the-google-plus-project/" rel="attachment wp-att-229477796"><img src="http://turbo.firstwaves.org/wp-content/uploads/The-Google-Plus-Project-e1310561957204.png" alt="Screenshot of the Introduction presentation for Google Plus" title="The Google Plus Project" width="600" height="339" class="alignnone size-full wp-image-229477796" /></a></p>

<p>Of course at the moment, it’s all seems much like the other services we know and love. <strong>This is not a bad thing</strong>. The fact that you can take your knowledge of Facebook (or Buzz etc) and move into Google+ is a huge bonus at starting time. If Google can layer more functionality over the top of this simple base, I imagine Google+ being a powerhouse of sharing and a massive database of knowledge.</p>

<p>This is just my initial reaction/summation of Google+. The best way to find out what it’s about is to give it a go. I’ve got some invites if you’d like to try it! Check out <a href="https://plus.google.com/101929452061447291902/posts">my +Josh posts</a> and put me in one of your circles. </p><p><a href="http://firstwaves.org/google-plus/">Google+ (or Google Plus if you wanna be search-engine friendly)</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<ol class="footnotes"><li id="footnote_0_229477777" class="footnote">or third?</li><li id="footnote_1_229477777" class="footnote">But is really – everybody knows, you guys</li><li id="footnote_2_229477777" class="footnote">not really deep down</li><li id="footnote_3_229477777" class="footnote">although I never knew why – it was pretty straight forward</li><li id="footnote_4_229477777" class="footnote">or exploded</li><li id="footnote_5_229477777" class="footnote">It’s also to make advertising more profitable, but that’s another story</li><li id="footnote_6_229477777" class="footnote">and see and click on more ads</li></ol><img src="http://feeds.feedburner.com/~r/firstwaves/~4/p4U4rWiDIBc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/google-plus/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://firstwaves.org/google-plus/</feedburner:origLink></item>
		<item>
		<title>Get excited again!</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/c0niC5CtrQg/</link>
		<comments>http://firstwaves.org/get-excited-again/#comments</comments>
		<pubDate>Wed, 06 Jul 2011 11:02:34 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Status]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477752</guid>
		<description><![CDATA[Since my last post more than a year ago, a lot has happened to Google Wave. Within months of opening Wave up to everyone at the Google I/O conference, Google pulled the plug, and Wave gurgled down the drain. That left me feeling somewhat foolish, as I’d dedicated a good portion of my time to [...]<p><a href="http://firstwaves.org/get-excited-again/">Get excited again!</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Since my <a href="http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/">last post</a> more than a year ago, a lot has happened to Google Wave. Within months of opening Wave up to everyone at the Google I/O conference, Google pulled the plug, and Wave gurgled down the drain.</p>

<p>That left me feeling somewhat foolish, as I’d dedicated a good portion of my time to Wave: joining a group of Wave Watchers((a group dedicated to helping new wave users and maintaining some sense of order in the fun chaos that was Wave)) and maintaining this website. I never expected Wave to gather much support at first, but I honestly thought it would last longer than it did. It certainly seemed to me to have more momentum than it turned out to have.</p>

<p>So when I heard they were killing it off, I was left figuring out what to do with this website. I had a couple of ideas:</p>


<ol>
<li>I thought I could change focus onto some other Google product, but honestly, none of them inspired me all that much: Buzz was a fairly bland FriendFeed clone that I couldn’t use from my normal account and messed up my Google Reader experience. </li>
<li>I could shift focus to a non-google product, but similarly, there was nothing all that awesome that I thought had much weight behind it. For instance, Novell’s Pulse was meant to be a Wave-like collaboration tool that was intended to federate with Google Wave itself – but Novell the company just doesn’t have the clout they used to have, and I knew Pulse wasn’t really going to take off. There are so many products out there that do much the same sort of thing, but they’re all these little walled-off social network wannabes.</li>
<li>I could continue with the open-source Wave project picked up by Apache. A few people are running with this, and it might be a fun project to monitor but it’s not moving as swiftly now that Google isn’t funding it.</li>
<li>I could generalise the focus to any product that might replace email as the fundamental communication of the internet. This would leave Facebook and Twitter and other Buzz-like products. This honestly appealed to me the most, but again the problem with most of these sorts of products is that they all live in their own little worlds and if I choose to use on Twitter for example, then I’m cut off from my wife who might choose to use Facebook.</li>
</ol>



<p>So I thought about it and then just ignored the problem and hoped it would go away. Plus I started a new job that required a lot of time and energy and in the end, maintaining a website about a product or products that didn’t inspire me just… didn’t inspire me.</p>

<p>But a few days ago, Google announced <a href="http://googleblog.blogspot.com/2011/06/introducing-google-project-real-life.html">Google+</a> (pronounced Google Plus if you couldn’t figure that out). It’s a “social networking layer” built over the top of some of their other products. It has some of the limitations of the products I decided not to focus on from the list above, but it’s got some promise and for the first time in a year, I’m excited about one of Google’s new products again.</p>

<p>So this site will now focus on Google+ for a while – until it takes off, or fails. My next post will explain why I’m excited by this, and why I’m writing about it when at first glance it seems no different to the products on the list. I’m also planning a newbie’s guide to bring non-techies up to date.</p>

<p>If you’re new here subscribe to the site! And if you’re a reader from long ago and my site’s just popped up again in your Reader, then Hi! Welcome Back! Thanks for sticking with me so long! Things are gonna ramp up around here!</p>

<p>It’s good to be back.</p><p><a href="http://firstwaves.org/get-excited-again/">Get excited again!</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/c0niC5CtrQg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/get-excited-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://firstwaves.org/get-excited-again/</feedburner:origLink></item>
		<item>
		<title>Google Wave Live and Available for Everyone! Including Google Apps users!</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/bHW792AsmLU/</link>
		<comments>http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/#comments</comments>
		<pubDate>Wed, 19 May 2010 20:11:13 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477740</guid>
		<description><![CDATA[Today at the Google I/O Conference (the same one that Google Wave was announced at last year) Lars Rasmussen gave a brief update on Google Wave. The biggest news is that Google Wave is now available for any one to sign up without an invitation. This makes it much more likely that large groups will [...]<p><a href="http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/">Google Wave Live and Available for Everyone! Including Google Apps users!</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Today at the <a href="http://code.google.com/events/io/2010/" class="vt-p">Google I/O Conference</a> (the same one that Google Wave was <a href="http://firstwaves.org/wave-preview-at-the-google-io-developer-conference/" class="vt-p">announced at last year</a>) <a href="http://firstwaves.org/?s=lars" class="vt-p">Lars Rasmussen</a> gave a brief update on Google Wave. The biggest news is that Google Wave is now available for any one to sign up without an invitation. This makes it much more likely that large groups will just get started collaborating on Wave without having to coordinate Wave invitations for everyone. While the service was invite-only it had the appearance of being a “tech elite” product. As more people found uses for it in group situations (classrooms, meetings) the need to make it easy for the people that actually <strong>wanted</strong> to use the product to do so became obvious.</p>

<p>In a <a href="http://www.huffingtonpost.com/lars-rasmussen/google-wave-open-to-every_b_581298.html" class="vt-p">guest post on the Huffington Post</a>, Lars explains:</p>

<blockquote>For this reason, today we opened up Google Wave to everyone. You no longer need an invitation to use the service. Simply go to <a href="http://wave.google.com" target="_hplink" class="vt-p">wave.google.com</a> and sign right in. Likewise, if you administer a Google Apps domain, you can now <a href="http://www.google.com/apps/intl/en/business/wave.html" target="_hplink" class="vt-p">easily enable</a> Google Wave for all your users at no extra cost. Google Wave is now officially part of Google Labs, the same place my team launched Google Maps close to 5 years ago.If you tried Google Wave earlier and found it not quite ready for real use, we think you’ll find that a lot has changed, and now is a good time to give it another look.</blockquote> <cite><a href="http://www.huffingtonpost.com/lars-rasmussen/google-wave-open-to-every_b_581298.html" class="vt-p">Lars Rasmussen in the Huffington Post</a></cite>

<p>Did you catch that second part? That was the other half of the announcement: Google Wave is now live for all Apps for Your Domain accounts! If you are using Gmail or Google Calendar on your own domain name, you can now use Google Wave too, and it integrates fully with the normal Google Wave experience. Those of you who have been waiting for this since launch, or since <a href="http://firstwaves.org/google-wave-for-apps-being-rolled-out-to-some-organisations/" class="vt-p">Linkoping University announced it</a> for their students, well wait no more!</p>

<p>It took about 3 hours from the announcement to being able to add Wave to my own domain account. Setup is a breeze. Click the “Add more services” link on your App Dashboard to install the Wave Preview. Then get Waving!</p>

<p>Don’t forget to <a href="https://wave.google.com/wave/wavethis?t=Contact+from+First+Waves&amp;r=josh@nunnone.com" class="vt-p">Wave @ me</a> and add josh@nunnone.com to your Wave contacts.</p><p><a href="http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/">Google Wave Live and Available for Everyone! Including Google Apps users!</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/bHW792AsmLU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://firstwaves.org/google-wave-live-and-available-for-everyone-including-google-apps-users/</feedburner:origLink></item>
		<item>
		<title>Wave This API released. Plus Official Chrome Extension and Bonus Unofficial WordPress Widget</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/9S4zNxC2eyc/</link>
		<comments>http://firstwaves.org/wave-this-api-released-plus-official-chrome-extension-and-bonus-unofficial-wordpress-widget/#comments</comments>
		<pubDate>Wed, 19 May 2010 19:34:43 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[addon]]></category>
		<category><![CDATA[extensions]]></category>
		<category><![CDATA[first look]]></category>
		<category><![CDATA[new feature]]></category>
		<category><![CDATA[official help]]></category>
		<category><![CDATA[use case]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477737</guid>
		<description><![CDATA[A new Wave API, a new Wordpress widget, and an undocumented use case!<p><a href="http://firstwaves.org/wave-this-api-released-plus-official-chrome-extension-and-bonus-unofficial-wordpress-widget/">Wave This API released. Plus Official Chrome Extension and Bonus Unofficial WordPress Widget</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<p>A few weeks ago, I noticed a <a href="http://firstwaves.org/new-wave-this-function-and-buttons/" class="vt-p">new feature</a> of Google Wave that allowed a user to easily send websites and content to a new wave to easily share with others. The feature (called “Wave This”) was not officially announced at the time, and I was asked politely not to say anything more at the time until the team could officially announce it.</p>

<p><a href="http://code.google.com/apis/wave/wavethis/" class="vt-p"><img src="http://turbo.firstwaves.org/wave-this-buttons.png" class="s3-img" border="0" alt="wave-this-buttons.png" /></a></p>

<p>In addition to this, the <a href="http://code.google.com/apis/wave/wavethis/" class="vt-p">Wave This</a> function has an <a href="https://chrome.google.com/extensions/detail/fdgmdpiobhnblhnhlmngalmeobbmofbm?hl=en" class="vt-p">official Chrome Extension</a>. Install the extension, and you can send any page to Wave with a click!</p>

<p>Finally, you can also use an undocumented Wave This feature to add a Wave contact button to your sites. At the top of my page I’ve added a “Wave @ me!” button that starts a new wave with me as a participant so you can easily contact me in Google Wave. To add the button to your own site it’s as easy as filling your details in the code below:</p>




<pre class="brush: plain; title: ; notranslate">
&lt;a href=&quot;https://wave.google.com/wave/wavethis?t=Contact+via+[Your-Site-Name]&amp;r=[fill-in-your-@-wave-address-here]&quot; title=&quot;Contact me in Google Wave&quot; class=&quot;vt-p&quot;&gt;&lt;img src=&quot;[your-button-image]&quot; alt=&quot;Wave at me!&quot;&gt;&lt;/a&gt;
</pre>




<p>The &amp;r parameter for adding a recipient isn’t listed on the <span class="caps">API </span>page and support might be pulled or altered so use at your own risk. Additionally, be aware that the Wave This function currently defaults to the Google Wave Preview account only, so if you use a different client (a Google Wave for Domain Apps account for instance, or Novell Pulse) you’re out of luck for now.</p>

<p>So there you have it! A new <span class="caps">API, </span>an awesome function, and my modest widget. Have at it! Make some buttons!! Start spreading Wave!!!</p><p><a href="http://firstwaves.org/wave-this-api-released-plus-official-chrome-extension-and-bonus-unofficial-wordpress-widget/">Wave This API released. Plus Official Chrome Extension and Bonus Unofficial WordPress Widget</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/9S4zNxC2eyc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/wave-this-api-released-plus-official-chrome-extension-and-bonus-unofficial-wordpress-widget/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://firstwaves.org/wave-this-api-released-plus-official-chrome-extension-and-bonus-unofficial-wordpress-widget/</feedburner:origLink></item>
		<item>
		<title>Get Your Wave Peeves Off Your Chest!</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/hkcJt_sdBEM/</link>
		<comments>http://firstwaves.org/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://firstwaves.org/get-your-wave-peeves-off-your-chest/">Get Your Wave Peeves Off Your Chest!</a> is a post from: <a href="http://firstwaves.org">First Waves</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://firstwaves.org/get-your-wave-peeves-off-your-chest/">Get Your Wave Peeves Off Your Chest!</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/hkcJt_sdBEM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/get-your-wave-peeves-off-your-chest/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://firstwaves.org/get-your-wave-peeves-off-your-chest/</feedburner:origLink></item>
		<item>
		<title>Remove: Remove Yourself! Remove Others!</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/Oja6Qc5HJf4/</link>
		<comments>http://firstwaves.org/remove-remove-yourself-remove-others/#comments</comments>
		<pubDate>Sun, 25 Apr 2010 07:28:20 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[new feature]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477709</guid>
		<description><![CDATA[The most long-awaited feature (besides the "seemingly dead":http://firstwaves.org/shortcut-on-buttons-interface-update/ "Draft" button) has "finally been imlemented by the Google Wave team":http://googlewave.blogspot.com/2010/04/removing-participants.html. That's right, "Remove Participant":http://firstwaves.org/lars-remove-participant-feature-due-within-a-month/ is here! What this means if you're not an addicted Wave user, is that wave authors now have total control over who comes and goes from their waves.<p><a href="http://firstwaves.org/remove-remove-yourself-remove-others/">Remove: Remove Yourself! Remove Others!</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<p>The most long-awaited feature (besides the <a href="http://firstwaves.org/shortcut-on-buttons-interface-update/">seemingly dead</a> “Draft” button) has <a href="http://googlewave.blogspot.com/2010/04/removing-participants.html">finally been imlemented by the Google Wave team</a>. That’s right, <a href="http://firstwaves.org/lars-remove-participant-feature-due-within-a-month/">Remove Participant</a> is here! What this means if you’re not an addicted Wave user, is that wave authors now have total control over who comes and goes from their waves.</p>

<p><img src="http://turbo.firstwaves.org/remove-participant.png" class="s3-img" border="0" alt="remove-participant.png" /></p>

<p>This is a <strong>big deal</strong> for Google Wave. The button has been there since the beginning, but grayed out and unusable. It’s taken some of the shine off Wave that until today you were unable to recall waves or remove people added accidentally.</p>

<p>It works in a pretty straight forward way. You decide someone should not be a participant any more and you click remove. The person who is removed sees a big red X on the wave in their inbox and opening the wave shows the last thing they were able to see before you removed them. If you remove them before they even open the wave, they won’t even know it existed!</p>

<p><img src="http://turbo.firstwaves.org/remove-from-wave-receiver.png" class="s3-img" border="0" alt="remove-from-wave-receiver.png" style="width:600px;" /></p>

<p>Part of me balks at the idea of removing waves right out from under their noses if they haven’t opened them. It feels somewhat dishonest – but it’s actually just fixing a email shortcoming! I think we’ve gotten so used to the idea that once something is sent, it can’t be unsent that it feels a bit weird to actually be able to do it again. Keep in mind though that this probably isn’t foolproof. If for example someone’s waves become “unsynchronised” while you are removing them from the wave, they might still see it – leaving you thinking that you got to it in time.</p>

<p>Another big issue in the months since launch has been Wave abuse. Waves have been destroyed by malicious (and accidental) addition of bots, or overwhelming the wave with large amounts of spammy text. At the moment, the best way to deal with this has been to reduce the abuser’s participation to “Read-Only” and report them to the abuse team. This remains the best way to halt an ongoing attack, but now it’s also possible to clean up after an abuser by removing the sign they were ever there in the first place.</p><p><a href="http://firstwaves.org/remove-remove-yourself-remove-others/">Remove: Remove Yourself! Remove Others!</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/Oja6Qc5HJf4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/remove-remove-yourself-remove-others/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://firstwaves.org/remove-remove-yourself-remove-others/</feedburner:origLink></item>
		<item>
		<title>Lars Rasmussen talks to CNET UK</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/JyUwjU1ZT8g/</link>
		<comments>http://firstwaves.org/google-on-wave-itll-be-five-years-before-we-can-say-this-actually-works-crave-at-cnet-uk/#comments</comments>
		<pubDate>Wed, 21 Apr 2010 12:40:22 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[future]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477711</guid>
		<description><![CDATA[But it’s not going to happen overnight. It will be five years before we can say “this actually works.” Lars Rasmussen on Google Wave via CNET UK. Told you soLars Rasmussen talks to CNET UK is a post from: First Waves<p><a href="http://firstwaves.org/google-on-wave-itll-be-five-years-before-we-can-say-this-actually-works-crave-at-cnet-uk/">Lars Rasmussen talks to CNET UK</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<blockquote>But it’s not going to happen overnight. It will be five years before we can say “this actually works.”</blockquote>

<p><cite><a href="http://crave.cnet.co.uk/software/0,39029471,49305480,00.htm">Lars Rasmussen on Google Wave via <span class="caps">CNET</span> UK</a>.</cite></p>

<p><a href="http://firstwaves.org/wave-on-slow-cook/">Told you so</a></p><p><a href="http://firstwaves.org/google-on-wave-itll-be-five-years-before-we-can-say-this-actually-works-crave-at-cnet-uk/">Lars Rasmussen talks to CNET UK</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/JyUwjU1ZT8g" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/google-on-wave-itll-be-five-years-before-we-can-say-this-actually-works-crave-at-cnet-uk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://firstwaves.org/google-on-wave-itll-be-five-years-before-we-can-say-this-actually-works-crave-at-cnet-uk/</feedburner:origLink></item>
		<item>
		<title>The Massive (but not Exhaustive) List of Wave Resources</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/-Olm-x6KACY/</link>
		<comments>http://firstwaves.org/the-massive-list-of-wave-resources/#comments</comments>
		<pubDate>Fri, 16 Apr 2010 01:08:28 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[community]]></category>
		<category><![CDATA[fun]]></category>
		<category><![CDATA[opinion]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[use case]]></category>
		<category><![CDATA[users]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477651</guid>
		<description><![CDATA[I'm going to lay out the sites and people I follow, and if you're a hardcore Wave nut, you might like to follow them too. These people all have my utmost respect and admiration for their writing and dedication to Wave.<p><a href="http://firstwaves.org/the-massive-list-of-wave-resources/">The Massive (but not Exhaustive) List of Wave Resources</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<p>When I started First Waves I wanted to keep my readers up to date with Google Wave news and keep on top of changes and updates as they happen. However, looking around the net I soon found many sites that already do a great job of keeping up with Wave news, and I hate the idea of rehashing the same stuff my readers could get at any number of excellent sites. So instead I have started to concentrate on larger news and “future direction” stuff here at First Waves, and I hope my readers are OK with the focus.</p>

<p>But I realise that many people <strong>do</strong> want up-to-the minute Wave information, so I’m going to lay out the sites and people I follow, and if you’re a hardcore Wave nut, you might like to follow them too. These people all have my utmost respect and admiration for their writing and dedication to Wave. I’ve included these sites in a Google Reader bundle called <a href="http://www.google.com/reader/bundle/user/16049416693875578456/bundle/The%20Best%20Google%20Wave%20Sites">Best Google Wave Sites</a>. If you trust my judgement, you can use the bundle to subscribe to all twenty-two feeds in just a couple of clicks! If you’d like to know more about the sites though, read on!</p>

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

<h3>Wave Users – Hints and Tips</h3>

<p>First and foremost, you cannot go past the Official <a href="http://googlewave.blogspot.com/">Google Wave Blog</a> – written by Googlers with news information and tips. If you only subscribe to one <strong>other</strong> site (ahem), this should be it. It’s kind of a no-brainer though so lets move on to some less obvious sites.</p>

<p><a href="http://www.theshinywave.com/">The Shiny Wave</a> by David Cook takes a look at useful waves, gadgets and bots as well as the latest important technological developments that could impact Google Wave. Once a month he profiles the work of a talented Wave developer, and generally keeps a close eye on the Wave development community.</p>

<p><a href="http://completewaveguide.com/">The Complete Guide to Google Wave</a> Alright, this isn’t a site to follow so much as a book, but it’s written by the enormously talented <a href="http://ginatrapani.org/">Gina Trapani</a> with <a href="http://adampash.com/">Adam Pash</a>. The site includes the entire book for you to read for <strong>free</strong>, or you can get it in <span class="caps">PDF </span>or full colour print versions for a very small fee. If you’re just getting started in Google Wave, there really is no other site you need to get your head around it.</p>

<p><a href="http://www.poojasrinivas.com/googlewave/">Google Wave Information</a> by Pooja Srinivas (a Googler) is a compilation of Wave guides Pooja has written. The focus is on brand new users who might find something like the Complete Guide (above) too complicated. It also covers some unusual and fun use cases for Wave.</p>

<p><a href="http://wavingatyou.tumblr.com/">Waving At You</a> by Russell Tripp is where Russell puts all his tips and information on Google Wave to “ease the learning curve” as he puts it. Waving At You and <a href="http://twitter.com/russelltripp">Russell’s Twitter account</a> are where I found a lot of my favourite Wave resources. His tips are simple, but always excellent.</p>

<p><a href="http://www.waverz.com/">Waverz</a> uses waves themselves to create the articles. Using the <em>wavearchive@appspot.com</em> bot, an archived html copy of a wave is made (at http://archive.waverz.com). You can then embed this archive in a page using some simple javascript (or php or python on the back end). Beyond this technical marvel though is an insightful site written by a number of Wavers including one of my fave wavers Jon Blossom and Dragon Silicon, who’s work I’ve only just discovered while writing this article.</p>

<p><a href="http://googlewavepossibilities.blogspot.com/">Google Wave Possibilities</a> by Tim Brown is another excellent source of Wave news. Tim is a “Wave Watcher” – a group of Wave helpers – and for good reason. His site is full of helpful information (like how to get started with particular bots), and Google Wave news.</p>

<p><a href="http://waveonbusiness.com/">Wave on Business</a> is focussed on how businesses might use Google Wave. The site incorporates presentations, use case scenarios and information on collaboration.</p>

<p><a href="http://wave-book.com/">Google Wave Book</a> by AndrÃ©s FerratÃ© is a companion site to the books <a href="http://oreilly.com/catalog/0636920000426">Getting Started with Google Wave</a> and <a href="http://oreilly.com/catalog/9780596806019">Google Wave: Up and Running</a>. It is more than just a catalogue for the books though, and contains insightful posts with tips and ideas.</p>

<p><a href="http://www.riding-the-wave-prasun.com/">Riding the Wave</a> by Prasun Nair has Wave news, but mixes in some news about other communications technology such as telephones. The posts cover Wave news and information on its future direction.</p>

<p><a href="http://www.googlewaveinfo.com/">Google Wave Info</a>. The latest news and information about Google Wave by an anonymous author. Some useful information.</p>

<h3>Wave Developers</h3>

<p>These sites are run by Wave developers for Wave developers and contain a mix of the technical and informative. If you would like to dive in to the nuts and bolts of Google Wave, these are a few of the best!</p>

<p>The <a href="http://googlewavedev.blogspot.com/">Google Wave Developer Blog</a> is the official blog for Google Wave developers. It’s full of tips and guides and helpful information for developers who are just starting out with Wave and for Wave gurus too.</p>

<p><a href="http://wave-samples-gallery.appspot.com/">Google Wave Samples Gallery</a> is the go-to place for new robots and gadgets as they come out. Primarily a teaching resource, the extensions here are tagged with how well they will teach you the concepts behind developing for Google Wave. An excellent source of useful bots too!</p>

<p><a href="http://www.onthetopofthewave.com/">On Top of the Wave</a> by <a href="http://www.onthetopofthewave.com/">Kiwibcn</a> is a site run by a team of developers to showcase their experiences developing for Google Wave. One of their most popular posts is how to <a href="http://www.onthetopofthewave.com/2009/11/develop-your-first-wave-robot-in-java-2/">Develop your first wave robot in Java</a> and clearly demonstrates their knowledge and their ability to teach.</p>

<p><a href="http://wave.to/">Wave.to</a> by <a href="http://www.twitter.com/wavedotto">@waveDOTto</a> is the home of the developers of the <a href="/its-easter-so-chill-out-try-wave-check-out-mr-ray-and-say-hello/">excellent Mr-Ray extension</a>, plus many more. These guys clearly know their stuff, and they are passionate about sharing it with the developer community and the public.</p>

<p><a href="http://withwaves.com/">With Waves</a> are a team of four developers who have created a number of popular extensions including <a href="http://withwaves.com/vote-for-mashable-content/">Amazon and eBay bots</a> that insert product listings into waves when you mention them. They have also released their <a href="http://withwaves.com/google-wave-extension-generator/">Extension Generator</a> that they use internally to build their own robots. That’s generous!</p>

<p><a href="http://www.masteringwave.com/">Mastering Wave</a> by Daniel Graversen follows the process of developing for Google Wave, as well as highlighting important Wave news and tips. This site is one of the first Wave sites I subscribed to.</p>

<p><a href="http://www.processwave.org/">Process Wave</a> is written by seven software engineering students, and follows their process of developing from <a href="http://www.processwave.org/2009/12/invity-behind-scenes.html">Invity</a>, a group management bot, to <a href="http://www.processwave.org/2010/04/screencast-of-modelling-tool-for-google.html">a collaborative modelling tool</a> integrating the open source <span class="caps">ORYX </span>software into Wave.</p>

<p><a href="http://go-wave.net/">Go Wave</a> hasn’t been updated for little while now, but has some good information about Robots, Gadgets and Embedding.</p>

<h3>Google Wave Sites by Region</h3>

<p>The following Wave sites are written for specific communities and are often in another language. <strong>This should not be a problem</strong>. I speak nothing but English, but thanks to modern internet translation software have no trouble reading and participating in these sites. If you subscribe to these sites in Google Reader you can use the built in translation function and you should have no troubles whatsoever.</p>

<h4>Spanish</h4>

<p><a href="http://www.wavesfera.com/"><span class="caps">WAVE</span>sfera</a> by David Alviz. David was an enthusiastic commenter here on First Waves, so I followed him back to <span class="caps">WAVE</span>sfera and discovered his site was in Spanish. Realising I was missing out on some excellent tutorials and news I subscribed as soon as I remembered that Google Reader does instant translation! I’m glad I did – David updates almost twice daily (!) and is an endless font of knowledge and excitement over Wave. Without David, I’d probably be missing out on all the other excellent non-English wave resources below.</p>

<h4>German</h4>

<p><a href="http://blog.gwaver.net/">Google Wave Surfer</a> by Thomas Friebel has news and information with particular focus on the Wave experience and how it is changing over time. The site also includes <a href="http://blog.gwaver.net/forum/">a forum</a> for users to share their wave experiences.</p>

<p><a href="http://www.waveinside.de/">Wave Inside</a> by Sascha Ahlers has shorter updates than Google Wave Surfer, but they are no less informative. A good resource for quick news.</p>

<h4>French</h4>

<p><a href="http://www.wave-france.fr/">Google Wave France</a> is maintained by three authors who explore Wave use cases and report updates and changes as they happen.</p>

<h4>Russian</h4>

<p><a href="http://google-wave-russia.blogspot.com/">Google Wave Russia</a> by Vadim Barsukov has some in-depth articles from <span class="caps">Q&amp;A </span>sessions with Lars “Google Wave” Rassmussen. Some of the content appears to be English articles translated to Russian, but there is some original content too.</p>

<h3>Everything else</h3>

<p>Of course, this list is not meant to be complete. There are authors I’ve not met, site’s I’ve not found and tweets I’ve not seen. There are sites like <a href="http://smarterware.org/">Smarterware</a> or <a href="http://www.readwriteweb.com/">Read Write Web</a> that often cover Wave news, but aren’t dedicated to covering Wave. As I come across articles like this, I’ll add them to my “<a href="http://www.google.com/reader/shared/user/16049416693875578456/label/google%20wave">Further Wave Reading</a>” list over on the left. I also re-tweet interesting Wave articles from <a href="http://twitter.com/firstwaves">@firstwaves</a> on Twitter. If you really want to be in the loop, follow my Twitter list of <a href="http://twitter.com/firstwaves/wave-genius">Wave Geniuses</a> too!</p>

<p>I’ve also left off a <strong>lot</strong> of good resources and people that can be found on Google Wave itself, as that will take another post entirely. <a href="https://wave.google.com/wave/wavethis?t=Contact+from+First+Waves&amp;r=nunn.joshua@googlewave.com" title="Contact Josh via Google Wave">Ping me</a> if you’d like to chat, and I’m sure I can help you find some great people, and useful resources.</p>

<p>If you know of some great Google Wave resources I haven’t covered, please let me know in the comments below!</p><p><a href="http://firstwaves.org/the-massive-list-of-wave-resources/">The Massive (but not Exhaustive) List of Wave Resources</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/-Olm-x6KACY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/the-massive-list-of-wave-resources/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://firstwaves.org/the-massive-list-of-wave-resources/</feedburner:origLink></item>
		<item>
		<title>New “Wave This!” Function and Buttons</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/dfG-c4GzXew/</link>
		<comments>http://firstwaves.org/new-wave-this-function-and-buttons/#comments</comments>
		<pubDate>Wed, 14 Apr 2010 12:19:56 +0000</pubDate>
		<dc:creator>Screenbeard</dc:creator>
				<category><![CDATA[Post]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[new feature]]></category>

		<guid isPermaLink="false">http://firstwaves.org/?p=229477655</guid>
		<description><![CDATA[I was visiting Pamela Fox's personal website, and noticed she had a _Wave This!_ button attached to ["her latest post":http://otherfancystuff.blogspot.com/2009/11/developer-relations-explained-nerdy-way.html]. Interested in what it did, I clicked it and it opened a summary of that post in Wave ready to share with others! I can't find mention of the feature anywhere, and I'm not sure if it's permanent, but a specially formatted URL takes a title argument, a content argument and passes it to a special new _wavethis_ function.<p><a href="http://firstwaves.org/new-wave-this-function-and-buttons/">New “Wave This!” Function and Buttons</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
]]></description>
			<content:encoded><![CDATA[<p>I was visiting Pamela Fox’s personal website, and noticed she had a <em>Wave This!</em> button attached to <a href="http://otherfancystuff.blogspot.com/2009/11/developer-relations-explained-nerdy-way.html">her latest post</a>. Interested in what it did, I clicked it and it opened a summary of that post in Wave ready to share with others! I can’t find mention of the feature anywhere, and I’m not sure if it’s permanent, but a specially formatted <span class="caps">URL </span>takes a title argument, a content argument and passes it to a special new <em>wavethis</em> function as shown:</p>

<p><pre class="brush: plain; title: ; notranslate">https://wave.google.com/wave/wavethis?t=[insert title]&amp;c=[insert content]</pre></p>

<p>Using a bit of <span class="caps">PHP </span>in WordPress and a plugin called <a href="http://blog.samsarin.com/samsarin-php-widget">Samsarin <span class="caps">PHP</span> Widget</a> (that allows php in a special widget) I created the <em>Wave This!</em> button over at the side. Feel free to use it!</p>

<p>The <span class="caps">PHP</span> I used was as follows:</p>




<pre class="brush: php; title: ; notranslate">
&lt;?php if ( is_single($post)) {
$excerpt = urlencode(get_the_excerpt());
$posttitle = urlencode(get_the_title());
?&gt;
&lt;a href=&quot;https://wave.google.com/wave/wavethis?t=&lt;?php echo $posttitle ?&gt;&amp;c=%22&lt;?php echo $excerpt; ?&gt;%22&quot;&gt;&lt;img src=&quot;http://turbo.firstwaves.org/wavethis-button-dark.png&quot; alt=&quot;Wave This!&quot; /&gt;&lt;/a&gt;
&lt;?php } ?&gt;
</pre>




<p>Simply install and activate the plug-in. Add the Samsarin widget to your sidebar and past the code in as you see it. It will only appear on post pages (not the front page).</p>

<p>I created a couple of button images you can feel free to use:</p>

<p><img src="http://turbo.firstwaves.org/wavethis-button-dark.png" alt="" height="39" width="200" /></p>

<p><img src="http://turbo.firstwaves.org/wavethis-button-white.png" alt="" height="39" width="200" /></p>

<p>So that’s the new <em>Wave This!</em> button. Go ahead and give it a try. If you’re a developer I’d be interested in seeing other ways to implement this.</p><p><a href="http://firstwaves.org/new-wave-this-function-and-buttons/">New “Wave This!” Function and Buttons</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/dfG-c4GzXew" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/new-wave-this-function-and-buttons/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		<feedburner:origLink>http://firstwaves.org/new-wave-this-function-and-buttons/</feedburner:origLink></item>
		<item>
		<title>8 Google Wave Competitors</title>
		<link>http://feedproxy.google.com/~r/firstwaves/~3/TJRwuPovdZk/</link>
		<comments>http://firstwaves.org/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://firstwaves.org/8-google-wave-competitors/">8 Google Wave Competitors</a> is a post from: <a href="http://firstwaves.org">First Waves</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://firstwaves.org/8-google-wave-competitors/">8 Google Wave Competitors</a> is a post from: <a href="http://firstwaves.org">First Waves</a></p>
<img src="http://feeds.feedburner.com/~r/firstwaves/~4/TJRwuPovdZk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://firstwaves.org/8-google-wave-competitors/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://firstwaves.org/8-google-wave-competitors/</feedburner:origLink></item>
	</channel>
</rss>

