Save Google Wave

The ridiculously confusing interface to the Wave loaded on this page, plus the fact that it takes 30 seconds to load and then runs like a dog, is the perfect explanation of why Wave is being shut down. It's almost like that's what they were trying to demonstrate.

I know the protocol is a bit complicated, but didn't they say a while back they're going to open source a reference implementation of the server? Is this it?: <a href="http://code.google.com/p/wave-protocol/" rel="nofollow">http://code.google.com/p/wave-protocol/</a><p>I do not know if that's a complete Wave server, or if it's missing a piece. But if it <i>is</i> a complete Wave server, there's nothing to "save". It's already been saved. You just need to run it yourself, and possibly support from Google for exporting your data once. If it isn't, maybe some people will fill in the blanks. If nobody steps forward to fill in the blanks then the demand probably wasn't there in the first place.

The most obvious feature Google should have invested 5,000 man hours in: making Wave seamless in GMail as a standard. If you are talking to another GMail user, Wave should be automatically turned on for that message. I do not understand why this wasn't deathly obvious to them from the day that they announced Wave at Google IO 2009.

No Please Don't. Google had the good sense and humility to let a failure fail. Don't y'all go fucking that up.

[Wait several minutes for a large complex unwieldy UI to load]

I say we take off and nuke the entire site from orbit. It's the only way to be sure.

Yes, <i>this</i> will work. <i>Everybody</i> listens to anonymous internet petitions.

Many of the problems wave aimed to remedy still stand. It's my hope that google will bow out gracefully, leaving behind the work they have done and allow other to pick up where they left off. This seems to be the plan, although they haven't open sourced the entirety of the effort.

I do think the announcement to kill it off was a bit early :(<p>- I use wave daily and have for a while for basic 'group meetings' with people who work remote.<p>I am also surprised that Google didn't keep it alive for internal use (where Gmail came from) ~ perhaps they have something entirely new in the pipe.

Its open source, save it for yourself.

I definitely want to see Wave saved.<p>Further, I'll argue that since Google effectively took away our common, central access to the EtherPad service (even though the source code remains), they in some sense "owe" the community the effort of giving Wave more of a shot -- although I expect a common response will be that "business doesn't owe you anything that doesn't make money (in an legal fashion)".<p>My other comments (e.g. interface, lack of documentation and post-launch publicity) are here:<p><a href="http://news.ycombinator.com/item?id=1578127" rel="nofollow">http://news.ycombinator.com/item?id=1578127</a>

I'd rather they just integrate Wave with Gmail, something that I wanted from the start. I had no use for Wave, on its own, especially in the early days when invites were slow to go out. For a long time, Wave sat there, unused. By the time more of my friends and colleagues got access, no one cared anymore. This is a shame, because Wave has tons of potential.

Warning: The petition just got overtaken by an army of trolls.

I have never understood the power of petitions.. no matter how many people add themselves to this petition will that make a difference? Will google change its mind if a 300 odd (or even 3000 or even 30000) people add themselves to this?

There's nothing left to save. Google has already added collaboration capability into their Documents and Buzz is what they went with for microblogging in their mail app. <a href="http://it.toolbox.com/blogs/future-of-work/google-wave-rip-40451" rel="nofollow">http://it.toolbox.com/blogs/future-of-work/google-wave-rip-4...</a> goes into 6 reasons why killing off Wave is the right thing to do.

Has Google ever sold off a product or service? They certainly acquire but if I am not mistaken it is also common practice for large corporations to rid themselves or projects they are no longer interested in and sometimes this involves a monetary transaction in their favor.

Funny. I wouldn't want to be in Novell's shoes now after having invested in building a product on top of Wave: <a href="http://www.novell.com/products/pulse/" rel="nofollow">http://www.novell.com/products/pulse/</a>

This site … it's like they turned Google Wave into a mix of <a href="http://YourWorldOfText.com" rel="nofollow">http://YourWorldOfText.com</a> and 4chan. THAT use of the technology would be awesome.

I never found out what Google Wave was for, so it is really not a big loss.

open source this thing so I can sudo apt-get wave, it would go good with googles, "don't be evil"-slogan.

.... not

nah

#savewave