Firstly, the chief question I receive both via email and Twitter is “How do I get a Google Wave Account?” The second most asked question is “How long do I have to wait?”

Let’s start with – How you get a Google Wave Account:

Don’t ask for an account anywhere else but with the links below. You won’t get one!

Instead, if you’re a developer, fill out the form at
https://services.google.com/fb/forms/wavesignupfordev/.

Or, if you’re not a developer, fill out the form at
https://services.google.com/fb/forms/wavesignup/.

These are the only ways to get an account. Tweeting “Can anybody get me an account?” is just spam.

Also, some folks have had trouble when they sign up when they get there invite. Make sure you see the proper confirmation page after you fill out the form. If you see the same form again, fill it out again, pasting in the email address used for registration and the code embedded in your invitation link at the bootom of the page (you may have to scroll down to see it). Just make sure you get that confirmation page before you leave!

While your waiting for you invite (which could take a few week) you may want to try out PyGo Wave Server. The following about the PyGo Wave server comes directly from the Google Wave Code page.

PyGoWave Server – The Headstart

I couldn’t wait until the guys at Google released their reference server implementation, so I decided to build my own in the meantime.

This implementation uses Django – a well-known python web framework – as its backend and is in a very early stage. Just as Google, I want to release it to the public as fast as possible.

In the end, this will eventually be a full-featured server implementation for easy use, extention and integration with your web servers and applications.

Note: All of the code is directly derived from Google’s published Wave API and protocol specification

You can (should before signing up, so you know what to expect) read their Architecutral Thoughts about the server here. But this is a great development. The Google Architecture Team has always stated that Google Wave success is based on and requires independent Wave servers. Having this so fast out of the gate is a great development. See the YouTube video below.

I signed up at the PyGo Wave Test Server and had quite an enjoyable experience playing with it. Not to mention, the time from sign up to playing with PyGo Wave took approximately 5 mins. All of the gadgets currently used in Google Wave are available to play with. It really is worth trying out while your waiting. You definetly get the Wave experience and you get to play with the Gadgets.

UPDATE: 2009-09-05

The PyGo Wave Server has been updated here is there updated Blog post (actually dated 2009-09-02, I’m a little behind) titled:

New and Improved

Ok here we go, since yesterday our latest “major” release is live, which is Version 0.3. I think p2k managed to implement all those features we descriped in our Roadmap .

The coolest new thing is definitely collaborative editing within waves. It’s now possible to write stuff within a wave and edit it collaborative with your fellow wavers.

And we did some improvements under the hood. As you can see we changed our URL to http://www.pygowave.net , you will be redirected to it, and all this stuff is now hosted on a seperated v-server just for pygowave itself. So only pygowave is going down if something breaks and not our whole server.

Furthermore PyGoWave is under https://www.pygowave.net available with SSL encryption. The SSL certificate itself was created by us and is not trusted, due to the fact that we do not have the money to buy a trusted one. Nevertheless its better than nothing =)

And last but not least we are now on ohloh, which is kind of an Socialnetwork for Programmers and OpenSourceSoftware. You can get to our project page here. Feel free to add us to your “I use this” list.

Keep up the great work guys! Visit the PyGo Blog Page and subscribe to their RSS to make sure you get the latest updates.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

The picture you see below is my Wave account using the Tweety Robot. The Tweety Robot was something that was done by the initial Google Wave development team and shown at the I/O 09 presentation. At the time, however, it was not very secure.

Then since they “put together an OAuth library to extend the Java Robot API that allows for secure authentication using 3-legged OAuth. (See oauth.net for a detailed explanation of the authorization flow). - Google Wave Blog ”

I was originally going to couple this together with my wp-wave-shortcodes embed to show my Twitter account on my webpage. However, you have to add public@a.gwave.com as an address to your wave in order to use a wave on a public site which, in turn, would allow anybody with a wave account access to my Twitter Feed Wave.

So, instead I took a snapshot and hopefully in the future you will be able to do this without compromising your Twitter account security. However, the feature, even as it is now is extremely useful. You can be logged into your Wave account doing many things and also have your Twitter account running right beside you in another Frame. One less app required. One more thing integrated with everything else.

This would be an important feature for the future. Being able to import your Twitter Feed on your own without having to sign up with the spam-peddlers would be a great step in the right direction.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.