Testing Google Wave
In May 2009 we first heard about Google Wave, a new, partly open source way of communicating. This graphic shows my message to Google, with which I applied to test Wave. I watched Arrington’s interview with Google Wave founders and couldn’t wait to try it.
Google, of course had a cute form inviting the public to apply to join the couple thousand Google employees who had been testing Wave. With all the talk of Wave replacing email, instant messaging, some social networking and some collaboration apps, I couldn’t resist.
As shown here, the invitation-application form invited ASCII art. Since this is Google and they’ll probably see it all in 10 pt Arial, I pulled out a few, small classics I knew would be well enough interpreted, including:
\__ … Star Trek TOS communicator
=====__—^— … Star Trek TOS starfleet ship, large
-_– … Star Trek TOS starfleet ship, small
=/\= … Starfleet logo
\V/ … Live Long and Prosper
Did I cute my way into testing Google Wave? I did indeed!
The partially open nature of Wave enables such feats as tweeting from within Wave, which I did while providing the instructions for same to new Wave testers in October. As I also tweeted that day, I recommend ‘11 Google Wave robots that add value in the enterprise‘ by @MarkFidelman.
Post updated in October, 2009. Here are a few videos I’d shared in the original, May 2009 version of this post:
Let me know if (or it looks like when) you get in. Cheers
Sure Rick, but I’ve no inside track, so ask your friendly neighborhood Googler. Star Trek ASCII is my only weapon (well, and some friendly neighborhood Googlers who I will ask).
Cute!
That is all.
This sounds like a Google idea, all right .
Anything of importance will be store all on their central servers.
They will release most of the source code as open. [which begs, if you are into open, why not all and why not develope it open to begin with?]
They will allow third parties to build their own wave services because they want the Wave protocol to replace email, which happens to be an online service for which they do not own the market.
This is a favorite part: “Google will be the only Wave service provider, but it is hoped that, as the protocol becomes standardized and the prototype server becomes stable, other service providers will launch their own Wave services, possibly designing their own unique web-based clients as is common with many email service providers.”. Isn’t that magnanimous!