Anyone got a spare Google Wave invite?

[limb_clock]

WHOSE RESPONSIBLE THIS!?

[benedictw]

Judging by current stability anyone using this for 'real' work right now would be out of their mind. If you want a workable collaborative word processor\spreadsheet use google docs!

Right now stability and usability is pretty much on the TODO pile. On a busy wave (like the, erm, Yakyak one!) its dead easy to loose track of new stuff - that should appear on the scrollbar.

Aside from that it does look like the new exciting timewasting activity. I wonder how hard it would be for someone to do a collaborative tetris or something.

[xav]

Judging by current stability anyone using this for 'real' work right now would be out of their mind.

QFTW. Right now it's not even populating the inbox for me, so I can't even get to the YakYak wave. It's an interesting experiment, but needs some serious work doing on it before it's even close to production ready.

Aside from that it does look like the new exciting timewasting activity. I wonder how hard it would be for someone to do a collaborative tetris or something.

One of the gadgets I spotted earlier was a version of Pong, so it should definitely be possible.

[Darkflame]

How would a collaborative tetris work?
Thats an interesting idea.
Plenty of vs Tetris made, but a co-op? Interesting.

[Thoughtcat]

Still no invite here

[benedictw]

How would a collaborative tetris work?
Thats an interesting idea.
Plenty of vs Tetris made, but a co-op? Interesting.

Bits of crap falling from the sky in a wide display. Each user is free to point + drag bits to where they want them to go. You might split the 'landscape' into sections. A section, when filled, makes the line disappear.

[piku]

It'll be interesting to see how they modify and add features to this as time passes. Right now it feels like all they're testing is the server's handling of heavy load, and the threaded chat stuff.

If they can integrate the other google apps like the calendar, email and docs it'd be pretty good for doing real work with.

They also need to test it with netbook sized screens... it's a bit cramped and deeply nested waves are very hard to read.

[The Caffeine Kid]

You're in the secret club-house then now, Piku?

[benedictw]

They also need to test it with netbook sized screens... it's a bit cramped and deeply nested waves are very hard to read.

Minimise the inbox (and/or the inbox\trash selector). You don't really need it when reading a wave.

[Darkflame]

I noticed a few minor things changed today, they seem to be updating regularly.
I got my bot talking for the first time too

[piku]

You're in the secret club-house then now, Piku?

Yeah, it's alright I suppose. I'm just not feeling the frothy-mouthed "wow" factor right now. I have full faith that Google will add their own little touches that make it work really well eventually though.

[Darkflame]

The client isnt so much the wow as the possibilities of the protocol underlaying it.
The idea of persistent, open, user-editable and near real time communication standard opens up a lot of possibilities.

[Kronos]

Yay got mine today, pretty cool stuff to play with whatever the server response times.

I bet Microshit wished they'd thought of it too haha

[Ollie]

Isn't there a flaw to this list? AIUI there's a delay between sending an invite and Google passing it on to the invitee; so within that delay, surely, the same people from the top of the list are going to get invited multiple times? i.e., names need to be crossed off when the invites are sent, not when they are received...

[The Caffeine Kid]

Hopefully that is how it's working. People have said in the thread when they have sent someone an invite so they can put a tick by their name and so the next one goes to someone else. That's the plan anyway, I believe.