it seems that Google has outdone themselves and recreated MS Outlook and Exchange. I couldn't find anything in the beta that a properly configured Exchange Server won't do.

Yea Google!

Yes, it is a trick to get stupid users to give away information. Google is a vampire that sucks the life out of everything. It's a real shame their search engine is so good. I won't touch their other stuff. (except Translator - just because I like the stupendously horrible translations it comes up with)

@Solomon Grundy

"I couldn't find anything in the beta that a properly configured Exchange Server won't do"

Except me and my friends do not happen to share access to a properly configured Exchange Server. Wave is presumably accessible to all Look at Facebook, people will give up their private details in a snap if it provides utility.

It doesn't help that its an extension to XMPP, which is not the internet's simplest protocol.

The authors assert the success of email was due to open protocols. I'd argue that the success of email was largely down to being a very very very simple and easy to implement protocol. SMTP sits directly on top of TCP. It uses ASCII. It uses half a dozen commands. That's it, it's simple enough to "implement" by hand, using telnet. No need for fancy API's. You could teach a ten year old to do it.

Wave uses XMPP, and this sits on top of TCP, TLS, and SASL, using XML, UTF-8, X509, MD5, base-64, URNs etc, which is great - much better than email - but has a lot bigger learning curve. You need libraries and APIs, frameworks, public key infrastructures, XML parsers, and so on. On the server side, I wonder if we will ever see the situation where practically every organisation on the net has an XMPP server and they communicate seemlessly (as we see now, more or less with SMTP).

Or will the complexity lead to a few big walled gardens like Facebook and Twitter?

Now google will be able to grab all the content from the other sites but replace the ads with their own. curious if they attract some of the same lawsuits that some online news aggregators have been hit with for doing that sort of thing (the content grab, not the flashy ui).

Hold up, so I have to have a default position of hating Google now, because it's big and ubiquitous and competes in the marketplace? More or less than Microsoft? I'm confused.

I've wished for ages that you could properly thread email conversations as sending entire chains in another mails is, frankly, pants.

@Solomon Grundy

"I couldn't find anything in the beta that a properly configured Exchange Server won't do"

Bullshit of the highest order. Exchange may well do mail, NNTP, calendars and allow attachments - but it does NOT aggregate the whole thing into one stream. If I have an NNTP chat about a doc in an emails - those are not correlated on Exchange - that's something I have to do manually.

@A prediction

"Wave is a stupid waste of time and how evil Google are using to con idiots out of their privacy."

This is a good point, but as the code is OpenSource and the protocol also open; there's nothing to stop me or anyone else creating servers/clients that do not chat to Google. In my line of work I can actually see some use for this - but on a bespoke fork and not using the browser. Whether or not we'd pursue that would greatly depend on the license used.

Talk to your admin or update to a newer version of Exchange. Yours obviously isn't working correctly.