The first 8 invites have gone, another 10 are available for those who email me at
bbohlinger [at ] googlemail [dot] com. Just get in touch.
My review of 14 November is available within my blog: My post on Google Wave’s potential.
It focuses on qualitative aspects of my own experience with Wave. Google have conducted a quantitative study and published their findings in a post highlighting statistics on what users like and dislike.
I strongly recommend to use Google Chrome which is a lot faster than Internet Explorer (add-in) or Firefox – in particular in larger Waves. Google Chrome works well even on mobile broadband, so worthwhile trying if you haven’t downloaded it yet.
If you are interested in more sophisticated waves for business or education and other projects, check this detailed blogpost that features a number of helpful screenshots: Lifehacker’s Google Wave for projects article.
I got an invite to Google Wave some time back and at the moment about half of my 11 contacts in Wave have engaged in some online collaboration. This was predominantly in 1:1 conversation, so very similar to emailing at this point.
One major exception, though. A wave that started on 6th November, includes in this hour 125 -invited- users (basically by friend’s snow-balling), and discusses the simple question whether Wave will become a success. So, it’s Yes, No or Maybe. Nearly 80 messages and comments have been generated and to me it’s been an excellent way to explore the limited options a little further. Wave Preview is restricted with respect to add- ins and gadgets. Here is a list of Google Wave extensions and Google Wave Robots that we are supposed to be able to use sometime soon (when exactly is still unclear).
Some users within this Wave declared they were getting impatient, this was the main argument people made who thought Wave is not going to be a success. However, this specific wave is managed (so people stay on the topic) and contains some gadgets. New comments are highlighted, in order to trace back when a wave was started and what was said by whom there is a playback menu, which also allows to toggle between frames and lists a full list of participants of a wave.
So far I find it very interesting to see how much speculation there is and how much misconception – this extends to those users who haven’t engaged in the managed wave. It seems the lack of communication provided by Google within Wave feeds into pessimism and the lack of time or curiosity to explore options and play equally nurtures the failure some see on the horizon. Those who are not familiar with editing wikis and collaborating in semi-private online spaces argue they want more privacy and control, others claims it’s boring and some said they would only log in to see whether someone had said something to them (which, I admit, made me instantly think about their real life relationships…).
Wave raises interesting questions as to power and control, censorship and regulation – on the micro-level of the individual user. Some seem to be very comfortable talking to anyone who has posted something worth commenting on. Others remain observers – at least they are still listed as such. Users can unfollow any wave, just like in Twitter. There is an option that allows users to tag a wave, so it’s collective tagging which is fun – and can help looking at discussions from a different angle, depending on the users’ expertise and professional background. Now there is also an option to up-and download a wave or copy it to another wave. The latter option made me wonder whether all comments are recognised by users as not copyrighted. Basically, Wave operates as password-protected area but I doubt every user holds the same authorship ethos – attribution may become an issue.
Wave is fast and operates well in Google Chrome but it seems to cause problems in other browsers. So far it has delivered it key promise: to provide the main features of Twitter, Facebook and Wikis, with a few more options and gadgets, this could become my favourite tool of discussion, in particular in combination with Google Docs.