And So Google Finally Announces the Formal Death of Google Wave in 2012...

And so at last comes the end of one of Google's most intriguing and useful collaboration platforms... Google Wave. Amidst the long list of services Google is killing off as part of its latest round of "spring cleaning" was this note about Wave:

  • Google Wave We announced that we’d stopped development on Google Wave over a year ago. But as of January 31, 2012, Wave will become read-only and you won’t be able to create new ones. On April 30 we will turn it off completely. You’ll be able to continue exporting individual waves using the existing PDF export feature until the Google Wave service is turned off. If you’d like to continue using this technology, there are a number of open-source projects, including Apache Wave and Walkaround.

I admit that from the start I was a big fan of Google Wave. I wrote about Wave a good bit here on this site and used it both personally and professionally. Wave's ability to allow real-time collaboration was really quite incredible, as I documented in this video about collaborative note-taking at a conference. In fact, I still use it weekly as Shel and Neville use Wave to plan the outlines for each For Immediate Release podcast - as a weekly correspondent I use the wave to see what else they are going to talk about to avoid overlapping or to build on what is being discussed elsewhere. They also get to see what I am going to be talking about in advance of me submitting my recording. It also provides an easy way for them to get the links for the show notes.

Plus, as an advocate for an "open Internet" where can control your own data, I loved the promise that the "Wave protocol" would allow for federation between Wave servers... that it would allow for the creation of a distributed and decentralized architecture for collaboration servers.

Sure, Google Wave had a user interface that was very "different" and took some getting used to. It definitely had some clunky aspects to it... and the massive hype around it led to outsized expectations that clearly could never be met.

And now, two years after Wave's launch, some of the features in Wave have migrated into other Google products. Google Docs has a real-time editing capability very similar to what worked so well in Wave. Google+ amusingly has the "play back" capability in its Ripples feature. There may be other features in other services I haven't noticed. It's clear that that work involved with Wave had an impact within Google.

Now it's left to open source projects like Apache Wave and Walkaround to carry on with what Google Wave started. It will be interesting to see what can be done... I'm certainly going to be exploring both projects in the time ahead.

Goodbye, Google Wave, 'twas nice knowing you...

If you found this post interesting or useful, please consider either:

Google Wave to rise from the ashes in open source form?


Ever since the announced demise of Google Wave, I think we've all been wondering what would be next and how much of the code Google would make available. Today, they've taken a step in that direction with this post:

Wave open source next steps: "Wave in a Box"

In the post, they say that they will make available as open source:

  • an application bundle including a server and web client supporting real-time collaboration using the same structured conversations as the Google Wave system
  • a fast and fully-featured wave panel in the web client with complete support for threaded conversations
  • a persistent wave store and search implementation for the server (building on contributed patches to implement a MongoDB store)
  • refinements to the client-server protocols
  • gadget, robot and data API support
  • support for importing wave data from
  • the ability to federate across other Wave in a Box instances, with some additional configuration

If they follow through on all this, it should be quite a good offering.  As they note:

This project will not have the full functionality of Google Wave as you know it today. However, we intend to give developers and enterprising users an opportunity to run wave servers and host waves on their own hardware.

After Google announced Wave back at that famous Google I/O presentation, I've been intrigued by it (and written about it) but what has most intrigued me is the possibility to move collaboration to a "distributed and decentralized" model in a way similar to email and web servers.  Distributed and decentralized is, after all, "The Internet Way", as I wrote about at great length in the past.

Let's see what happens... and I, for one, will definitely be watching to see what they make available.

What do you think?  Can Wave re-emerge as something useful?

If you found this post interesting or useful, please consider either:

5 Steps to Enable Google Wave for Google Apps accounts

googlewavepreview.jpgWith Google Wave now being available for everyone, and specifically now available for businesses using Google Apps, I thought I'd just post the 5 steps of how to enable Google Wave for your Apps account. (The steps appear in the video on the Google Apps page, but you have to watch the video to know that.)


You have to be the administrator for your Google Apps domain in order to enable Google Wave.


Next to the "Service settings" heading there is a "Add more services" link. Follow that link:



On the next screen, you just select the "Add it now" button:



Google throws up a page just warning you that you can't get support for Wave through existing support contracts... and other warnings. Just hit the "Yes, enable Google Wave" button:



That's it. Now you can just direct people within your Google Apps domain to go to:

and they can start waving! Here's what it looked like for me:


Now, as noted in the warnings, users in your Apps domain can by default also invite external people into your corporate waves. That may be a great thing... that may be something you want to think about.

In any event, enjoy waving within Google Apps!

If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or subscribing to my email newsletter.

Can't attend Google I/O this week? You can follow along in Google Wave.

Remember Google Wave? The big buzz that we all talked about last year? (And that I wrote a good bit about here.) While some of us may have reduced (or dropped) our Wave usage, Google is naturally using it heavily and as 5,000+ developers all gear up for the big Google I/O conference this week in San Francisco, the word is out that you can follow along in "Live Waves" during the event. This big URL should take you there (assuming you have a Wave account):,!w%252BeRiTZrZkCcw

You should see something like this:


Note that if you are already in Wave you can simply enter this in the search box:

group:[email protected] tag:io2010

If you aren't familiar with the idea of using "live waves" for conference note-taking, you may want to view my Emerging Tech Talk #40 video podcast where I demonstrated how Google Wave could be used this way.

Note: Thanks for Jay Cuthrell for tweeting out this info.

P.S. If you are out at Google I/O, please say hello to our Voxeo Labs team who will be in the Google I/O Sandbox demonstrating Voxeo technologies and how they work with Google services

If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or subscribing to my email newsletter.

The Single Biggest Reason Why I Can't Yet REALLY Use Google Wave

googlewavepreview.jpgI'm a big fan of Google Wave. A huge fan in fact. I've written about it, posted a screencast about using it in conference collaboration and have much more about it in my writing queue. I love the promise of the Wave protocol that will allow for distributed/decentralized collaboration that is in line with "The Internet Way". I've been a long-time fan of the XMPP protocol that is underneath it all. There is so much great potential in Wave.

But I can't really use it today.

Not yet, anyway.

It's NOT because of the common sentiment I hear about not having anyone to communicate with on Wave. Between Voxeons trying it out, PR/marketing folks associated with FIR trying it out, and a whole lot of other early adopters I know, there are probably easily 150-200 people that I could use Wave with.

And I very definitely can use Google Wave for PUBLIC Waves like those I described for conferences in my screencast. For public waves, it's great and works well.

But I can't really use it for true collaboration with a team a people - and therefore can't really push Wave to see what it can do.


Two simple pictures illustrate the issue:




Figure it out?

Yes, indeed....


Like I alluded to earlier, no big deal for a public wave. Public waves are by definition, well,... public... and so anyone can join in a public wave. And anyone contributing to a public wave should realize that anything they type there is potentially visible to everyone. It is an annoyance that you can't leave a public wave... but that's it.

(Note: the Google Wave team did hear the cries from Wave users and have allowed anyone to remove a bot from a wave. So bots can be kicked out, but not people.)


I'll give you two examples, though, where this is a huge problem.

First, imagine that you are trying to use Google Wave to collaborate on, say, a news release for your company. The content of the wave is confidential. You invite your team into the wave and you all work on the document. Then, because the current Wave user interface is, um, not entirely intuitive, one of your team members accidently adds someone from outside of your company into your confidential wave.


There is no way to boot that person out. In fact, via Playback, he/she can see everything you have ever typed into that wave... every edit... every snarky comment...

All you can do at that point is: 1) appeal to the person's brother/sisterhood as a fellow early-adopter to excuse the problem and try to pretend they don't see everything going on in the wave; and 2) start a brand-new wave (copying content over) that includes just your team and not this person.

Not ideal solutions.

Second, let's say that you are working with a team of people and one of the people decides to leave the team. Maybe they quit or are fired from the company. Maybe they start a competing project. Whatever the case... you don't want them to have access to the Wave any more.


copytonewwave.jpgAgain, no way you can remove them. The best you can do is go up to the upper right corner of one of the "blips" in your wave and do the "Copy to new wave" command... and then add everyone to this new wave.

I recently had to personally do this for a wave of 25+ people. Not a fun experience, particular because the current Wave UI only seems to let you add one person at a time. So I had to create the new wave and then figure out who all was in the old one and add them one at a time to the new wave. It didn't take a long time... it was really only a few minutes... but it was a pain. And then I had to flip between the old and new waves to be sure I had brought everyone over.

And then, since everyone would still see the old wave in their inbox, I had to change the title of the old wave so that people would not go into that one and would know they could archive it to get it out of their Inbox.


As The Complete Wave Guide indicates, it's not necessarily an easy problem to solve due to Wave's collaborative nature. Having said that, the problem has been solved in the IM space in places like Skype Group Chats, IRC channels, etc. Now, federation isn't here yet, but Wave's distributed and decentralized architecture could add some interesting syncing challenges to this issue - but yet it still seems to me to be solvable.

As "GeekLad" notes in "5 Reasons Google Wave Is Not Ready, it's an issue of lack of any real kind of "access control". I agree with with GeekLad that something like this kind of system needs to be in place:

  • Allow the wave creator do add/remove any participant from a wave.
  • Allow the wave creator to assign/modify the following permissions that can be set at the wave and participant level:
    • Permission to add bots to the wave.
    • Permission to invite other participants to the wave.
    • Permission to remove participants from the wave.
    • Read-only or read/write access to the wave.
    • Permission to grant/modify each (or all) permissions for other participants and/or the entire wave.

That's what we need.

Access control and the ability to remove participants from a wave.

Until that time, as much as I dearly want to be using Google Wave for all sorts of collaborative development... I won't... I can't in good conscience do so with private information.

Here's hoping that the Wave team does give us this feature real soon now... until then... I'll keep using it for public waves, and for non-confidential private waves... but I want to use it for so much more...

If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or

VIDEO: How to use Google Wave for Collaborative Conference Note-taking

googlewavepreview.jpgOver the past two weeks, I've both witnessed and participated in an incredibly powerful way to use Google Wave. The use case is simply this:
collaboratively taking notes at a conference

I saw this first Oct 28-30 at eComm Europe in Amsterdam. Members of the Google Wave team set up some initial waves and showed "live waving" during the actual event. Others then participated in (everyone at eComm was given a Wave account). I joined in asking some questions and participating in the dialog. Although I wasn't there, I wound up learning a lot of what went on there and now there are some great notes people can reference about the sessions. If you have a Wave account, you can see the eComm waves yourself by going to the search box at the top of the center column (where it usually says "in:Inbox") and entering in:

tag:ecomm with:public

Now you will see all the public waves that were created by multiple people during and after the event.

At VoiceCon and Enterprise 2.0 this week in San Francisco, I and a number of others did our own "live waving" and the process was quite powerful in cases where a number of us were collaborating. You can see the waves in Wave by searching on:

tag:voicecon with:public
tag:e2conf with:public

There weren't as many Wave users at the two conferences, so we didn't have quite as many collaborators in some of the public waves - but look at the ones relating to "Google Wave" to see some strong collaboration.

I actually used ScreenFlow on my Macbook Pro to capture one of the editing sessions, because I think you really need to see that in action to fully appreciate what it can do. I'm hoping to edit that and get it up as a screencast soon.

To show how to use Wave in this manner, I created this Emerging Tech Talk screencast based on the eComm public waves:

The Emerging Tech Talk blog post has a few more details about what I showed in the video.

If you use Google Wave in this fashion, please do leave a note letting people know how to find your waves. As we all explore this early preview of Google Wave, it's great to learn from each other.

If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or

Which is easier to understand? Google Wave or the Swedish Chef?

Heh... you just knew it was only a matter of time before the parody sites came out! Kudos to whomever put together:


Very cute.

The reality, too, is that Google Wave is hard to understand until you wrap your brain around the not-overly-intuitive user interface. Once you start to get the interface, though, there are some VERY cool things you can do with it... I've got some screencast ideas I hope to be posting soon...

If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or

Experimenting with Google Wave? Here's a great list of keyboard shortcuts

googlewavepreview.jpgAre you experimenting with Google Wave and wish you could work quicker within the Wave windows? If you are like me and love keyboard shortcuts, I found this site that may be of help to you:

The two shortcuts that save me the most time are:

  • "Shift+Enter" - ends your editing, the equivalent of pressing the "Done" button with the mouse.
  • "Ctrl+Space" - marks all blips in a Wave as read (important in a wave like the VUC Wave that has lots of commentary).

What Wave keyboard shortcuts do you find most useful?

P.S. If you are on Wave and want to say hello, I'm at "[email protected]".

P.P.S. No, I don't have any more invites. :-)

If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or

Today's launch of Google Wave - some links and initial thoughts

googlewavepreview.jpgUnless you were under a rock, or are not in the tech part of the online world, you knew that yesterday into today was "the big day" when Google Wave launched it's wider public preview. Having had a Wave login since back in July, but not honestly had a whole lot of folks to try it out with, I was pleased to get the invite this morning to join in the public preview. If you are in the world of Wave, I can be found at:
[email protected] [email protected]

Feel free to invite me to a wave. [UPDATE: It appears that within Wave, you have to use the "" address.]


There were, of course, a zillion stories written over the past couple of days related to Google Wave. Some of the ones I found most useful in understanding the basics:

Mashable has also had extensive coverage over the past few months, as has RWW in particular.

There were some other posts I found interesting:

The demo, in particular, was quite compelling and intriguing to see how Google Wave could fit into existing business apps like Salesforce.

With ANY service that was so incredibly hyped as Wave, there was the inevitable backlash... predicted by a TechCrunch article, chronicled by a RWW piece and certainly given the greatest roasting by none other than Robert Scoble himself:

Many, many, many more posts out there, naturally, and I'm sure many more will come in the days and weeks ahead as more people try it out. (I would also be remiss if I didn't point out Dion Hinchcliffe's great post from back in May: "The enterprise implications of Google Wave - Definitely worth a read.)


As I worked with the public preview today, I did have some initial thoughts:

  • Overall, I definitely LIKE it - Having worked with it for a while, I have to say that the potential for near-real-time collaboration is pretty amazing. It's great to see the ecosystem of applications (gadgets and robots) developing. The preview seems pretty fast and stable. And it's all built on XMPP and other open standards with the promise of a distributed architecture. All in all pretty impressive.

  • UI takes some getting used to - Having said that, the user interface to Google Wave does take some getting used to. Just the way comments are inserted... it's part IM... part email... part wiki. You might be leaving a comment toward the bottom of a wave when someone else inserts something toward the top. Just takes a bit to understand.

  • Namespace shared with GMail - This is either a good thing if you have a GMail name you like, or an annoying thing if you were hoping to get a particular name. In my case, I had perhaps naively hoped that maybe I could get "danyork", but since someone else has that for GMail already, I couldn't. So I wound up using my GMail account name. To be honest, it makes sense for Google to do it this way. There will just be namespace collisions for people like me with common names. So it goes.

  • Yet another place to check for messages - Both Louis Gray and Robert Scoble mentioned this, and I definitely agree... your Google Wave inbox becomes yet another place to check for messages. I already have a work email account, a personal email account (well, several, but all coming into one client), a Skype IM account, a dozen other IM accounts aggregated into Adium... so in addition to checking all of those I need to check my Wave inbox. And because it is web-based I don't have a way in my Mac's Dock area to know there are new messages. Hopefully at some point it will be integrated with GMail or provide some other way to help us with this issue.

  • Distributed architecture isn't there yet - I realize that this is only a "preview" for 100,000 people, but I'm impatiently interested to see the distributed architecture outlined at As I recently wrote about at great length, the "Internet Way" is to have distributed, decentralized architectures. Services like email or the web where: 1) anyone can set up their own server; and 2) you don't have to ask anyone for permission to do so. Google Wave holds out the promise of giving us a very rich collaboration infrastructure built on a distributed, decentralized model. I want to get there. Today. :-)

Those were some initial thoughts... I'm sure I'll have more as time goes on and I'll write about them here.

What do you think? If you are in the initial preview pool, what has your experience been?

If you found this post interesting or useful, please consider either subscribing to the RSS feed or following me on Twitter or

Tomorrow is "Google Wave Day" - some links to learn more...

If you're in the tech part of the blogosphere, you are probably aware that tomorrow Google will send out 100,000+ invites to Google Wave. It's a big deal, really, as a larger audience gets a view into what Wave is all about. Thankfully the folks at RWW put together a great post: For those wanting the "official" Google perspective, here you go: Now if only I could remember my %#$#% password to get into my Wave sandbox account, I could find out tomorrow how to get set up in the "real" Google Wave.

I'm looking forward to seeing Wave in action with a larger audience!