So it's a combination of an email client, Sharepoint and an RSS aggregator? (I'm only halfway through the video so I might not have seen all the aspects of it).

I'm just imagining trying to explain this to people I've worked with; the ones that had problems getting their heads around having to log in to Novell to see the shared drives; the ones who tell me there's a problem with Outlook when we use Lotus Notes.

Also, does all of the Wave stuff have to go through Google's servers? Or does all this stuff about APIs mean that people can set up their own internal Wave servers? Other questions too, but it's too early to get the words out right.

Yeah, I just got to the bit of the video with the two separate Wave systems.

I'm still not sure what to make of it. I doubt it'll replace email, simply because some people somewhere are bound to refuse to use it because it comes from Google, the new Microsoft. For most people I think it'll just be another username/password to remember, and another page to keep open in a browser tab.

Plus there's a good chance that Google will at some point go "meh" and half-forget about it. A bit like Google Docs.

It all depends on what developers can make out of it, I suppose, and I ain't one of those.

I wonder what the server and bandwidth specs would need to be to host your own system.

And would companies be happy with their employees collaborating with other companies employees, even if they're a trusted partner, if the data has to go through the Google server? There was some mention during the Federation part of the video about private replies and them not going to the Google servers, but I'm not sure whether that was just because the private replies were between two people on the same private Wave system.