I haven't blogged for a little while, and my only excuse is that I've been concentrating on doing rather than writing about it.
Anyway I thought I would put down some notes about the stuff I've been doing with Google's Wave and the avalanch that has been the launch of the new Beta Preview.
Firstly I should mention the new area I've setup for the work I am doing with Wave. http://wavingtheshiny.collaborynth.com.au/ is basically my Wave workspace, where I'm going to work on a range of different projects, from an embryonic book about the FedOne Wave Reference Server to a wiki that will contain information about the different Wave related projects I'm going to be working on.
Okay, next up, I am so sick and tired of seeing the "We have 000's of invites" spam awash on twitter and other places. Please people if you are looking for an invite, hit up wave.google.com this is the only legitimate place to sign up. Do not randomly beg people for an invite, do not believe the people who claim that if you just fill out a form and sign up for this free offer you're in like Flynn.
Right now for the hype. More has been written about Google Wave over the last week than since the IO Conference. This is understandable, all of a sudden a whole lot more people are getting a real look at the Googles system and seeing what it can do for them. I would like to make a couple of points though:
A couple of hints and tips for new wavers:
Making Public Waves:
Okay so you've got the wave and you want to talk to other people, or you want to start a wave for people of similar interests. Great. There was a facility to do this on the Wave Sandbox however it is a little broken.
The facility used to make a wave public is added just like any other robot or participant. You need to add the following address to your contact list: public@a.gwave.com. As I said this is slightly broken so you need to do the following:
What Browser:
For the moment, I'd use Chrome if you're having a play around with the Wave. Firefox 3.0.x tends to be really dog like and even Firefox 3.5.x can be slow. Chromes Javascript engine seems to be able to handle the heavy work involved with the wave interface. I haven't tried with any of the IE's or Safari.
Comments
Browsers and federated servers
Have you tried google's client in chrome/chromium under Linux? I've been sticking to firefox just because I thought Gears was basically a necessity.
Also, I've only just tonight set up my fedone server doing federation properly. Uh.... I think. Pings seem to work properly, but I haven't been able to find an echo agent or anybody else around to properly check it.
Re: Browsers and Federated Servers
I'm using chrome/chromium under ubuntu at the moment, specifically the nightly build which can be found here:
https://launchpad.net/~chromium-daily/+archive/ppa
If you want to test out federation you can try me at purserj AT wave DOT collaborynth DOT com DOT au or you can try my echoey agent at echoey AT wave DOT collaborynth DOT com DOT au