![](\"http:\/\/www.wave-invites.clickstuff.com\/google_wave_logo.png\"){kind=logo}
<\/p>\n<\/p>\n
Thanks to the kind invitation of S. Anthony Iannarino<\/strong>, I have been on the much vaunted, often coveted, \u00a0Google Wave<\/strong> <\/a>beta app ( I do not have any invites yet, sorry ) which mashes up email, realtime transparent instant messaging, other embedded web 2.0 apps and a wiki-like functionality. The interface looks like this ( from O’Reilly Radar<\/a><\/strong> – who can explain Google Wave far better than I can<\/a>:<\/p>\n What is it like?<\/p>\n First, for me, it’s a small handful of my blogcircle ( most of who are techies) milling about chatting, trying to figure out the functionality. The champ so far is Sean Meade<\/strong><\/a>, who is Tom Barnett’s<\/strong> <\/a>webmaster and also\u00a0the web editor for ARES<\/strong><\/a>;\u00a0Sean assembled a tutorial “wave” for the rest of us that I have just begun to plod through. It is not easy to find other googlewavers which is why people are posting calls on Facebook, Twitter and other social networking sites.<\/p>\n Secondly, this is a very unfinished symphony of a beta – at least compared to prior beta experiences I’ve had. Sliderocket<\/a><\/strong>, by comparison was very smooth and\u00a0probably 95 % ready when I received a beta account while with Google Wave I’d anticipate significant differences before it becomes generally available. As it is going to be open source, the potential creativity for future apps is vast.<\/p>\n Cool, interesting, not entirely sure how I will eventually use it on a regular basis yet.<\/p>\n \n![](\"http:\/\/radar.oreilly.com\/upload\/2009\/05\/Google_Wave_inbox_chess.png\")
<\/p>\n