Anyone got a spare Google Wave invite?

[Barney]

Didn't see this message til just now. Oops.

Are you sorted yet Chunk?

Yes, I took care of it

[bumblebee]

Is anyone using Wave in some productive way by now?

I just noticed that not only has it become faster, but they have a big number of collaborative extensions and also the ability to invite someone outside wave to a given wave by email. This should open the platform significantly. What's interesting to me is if anyone has made it practically usable.

[WiteWulf]

I'll be waiting until we can actually run our own Wave server at work before we start using it seriously. I was impressed by the concept back when we started this thread and am certainly eager to try using it in anger now.

[BrianTheNaughtyBoy]

I've used it to put together a report with a colleague. We needed to discuss data and decide on specific anlyses so it was pretty useful to organise the structure using wave. Otherwise it would have ended up with numerous emails back and forth with attached .xls files. It was pretty neat, though we haven't used it since (but probably would do for similar projects). It has potential to be useful, but I don't think it's going to change the way we work.

[teamonkey]

I'll be waiting until we can actually run our own Wave server at work before we start using it seriously. I was impressed by the concept back when we started this thread and am certainly eager to try using it in anger now.

Yeah, it would be great to use it at work. No way we could use it with public servers though.

[chub]

Google Wave is being axed: http://googleblog.blogspot.com/2010/08/ ... -wave.html

[Thoughtcat]

http://www.bbc.co.uk/news/technology-10877768

Google chief executive Eric Schmidt said it was hard to say why Wave did not strike a chord with a majority of users.

"It's a very clever product. You never know why it didn't work."

You can be too clever, you know, Eric... too hard to use, kept crashing, not really clear what I would use it for. And I'm reasonably geeky. Which means I couldn't get any friends who were not even slightly geeky to use it, which was the main problem.

[BrianTheNaughtyBoy]

It was meant to replace email, but clearly was never going to. I wonder if they'd tried to integrate gmail into it it might have become a little more useful. Some sort of "convert this mail to wave?" feature might have worked.

Oh well, nice idea. Shame.

[Darkflame]

They actually had a convert-site-to-wave feature, and it was a lot more stable over the last 6 months compared to the first.
(I haven't had a any crash in a month or two now).

The insanity is chucking out the Wave Federation Protocol support with it. Google (for once) failed at the GUI/public use area. But the core protocol has very little to do with it. Google did a front-end web implementation that people didn't like and now seem to be running of in a huff over it.

PyGoWave is still apparently continuing development, but thats only a few guys really. I see a few other servers up and about but the hopes for a federation is very low now. Google just handed the internet to Facebook really. Buzz isn't going to do anything, and there isn't any distributed, open alternative to facebook.

[teamonkey]

It would have quite happily replaced a variety of documentation methods we use at work. No way in hell we were going to do that on Google's servers though.

If they'd actually made it usable and got it to a stable state where they could distribute it with their Google Enterprise product (and an open source alternative), it would have destroyed a lot of wikis and forums.

Google are getting worse at finishing things.

[foxyloxy]

RESULT!

[Darkflame]

These guys made it intergrate with Outlook;
http://www.wavelook.com/

Also, they were releasing a server solution for enterprise users;
http://www.wavelook.com/server.html

If they'd actually made it usable and got it to a stable state where they could distribute it with their Google Enterprise product (and an open source alternative)

Well, no for Enterprise, but I think they are probably going to release almost all of it as open source.

A little bit of information on one of the google groups;

Hi everyone,
(In case you missed it, Thomas is referring to a recent blogpost:
http://googleblog.blogspot.com/2010/08/ ... -wave.html)
This is very recent news and we're in the process of figuring out exactly
how we scale down the engineering effort within Google. As for what it means
for the wave federation protocol, it is also an open question: there is
certainly an opportunity for continuing this community effort. If you've not
been following along lately, there was a recent talk at OSCON which includes
an overview of who is using the protocol so far, and what code is available.
The slides are embedded in this live wave: http://bit.ly/oscongwtalk
We'll share more information when we know more about Google's plans. In the
meanwhile, we're continuing our work to open source more of our source code
and do some clean-up on the existing open source code.
We recently open sourced Splash, a new (currently read-only) client
interface built on top of the Wave Data APIs, which you can find and use:
http://code.google.com/p/wave-protocol/ ... stallation
Additionally, we've submitted a patch to Apache Shindig that contains the
code for the wave gadgets JS API:
https://issues.apache.org/jira/browse/S ... .atlassian...
You can watch the wave-protocol-code-discuss forum (
http://groups.google.com/group/wave-pro ... de-discuss ) to see more code
releases as they happen.
Regards,
-Dan

[Darkflame]

And, to bring this thread around into a circle, you can now sign up for another company's Wave server/web gui beta here;

http:\\wavelook.com

[Ollie]

And, to bring this thread around into a circle, you can now sign up for another company's Wave server/web gui beta here;

http:\\wavelook.com

Christ, you have to use Outlook. Screw that.

[Darkflame]

That was my reaction at first too.
However, the outlock thingy is already out, the beta is for their totaly web based GUI.