Very much so. I'm a bit of a client-fetishist, and so I'd rather see Wave be broken down into a protocol and server, allowing for client applications to access

Very much so. I'm a bit of a client-fetishist, and so I'd rather see Wave be broken down into a protocol and server, allowing for client applications to access the wave, rather than deal with a web app, which still tend to lag behind a nice cocoa app. The nice thing about email and IM is that they're very KISS, message goes from client - server (sometimes) - other client. Wave was built with the Google mindset of server-server with web-only clients. Sure, there was the CLI app, but it was more of a proof-of-concept than Outlook or even Mail.app for IMAP. In terms of a project, Wave would greatly reduce the overhead of emailing in my project teams. We do web development, and there's a designer, PM, writer, AM, outsourced QA, and me, the developer. Right now there's this huge, hulking in-house business tracker meant to coordinate between the parties. Using a wave per site would be great, as we could all communicate on the same whiteboard. If you're still doing real-time collaborative, SubEthaEdit or ZoHo notes could fill the gap. Or, you could host the server yourself?