Brent Sordyl's blog

this post outlines how you’ll probably use Google Wave in the future and also gives you advice on how to implement it in your company or your team of coworkers. It also reveals some big usability problems in the current version. Those issues aside, I would like to show you the advantages of the “wave” once again and describe some cool use cases that might make you love it at some point in the future.
(Link: Why Google Wave Sucks, And Why You Will Use It Anyway)

Well, we’re not sure that last criticism can stand anymore. Because, whoah, check out what this guy did with Wave and a scene from Pulp Fiction:
(Link: The Best Google Wave Demo We’ve Seen Yet (NSFW) (GOOG))

Seems that most still believe Google Wave primarily uses XMPP to pass data around. Turns out, XMPP is only used for server to server federation. Joe Gregorio has a good overview of the actual APIs and protocols used in Wave, but I still found it easier to create a diagram:
(Link: Cubicle Muses – Wave’s Web of Protocols)

Put plainly, Wave is a message board in a constant state of self-editing flux. To put it another way, it’s a collaborative text editor on steroids — as our mobile editor Chris Ziegler quipped, “I think Wave’s capabilities actually exceed human capacity to interact.” There’s a lot of great ideas here, many we’d love to see find their way into other Google apps, but we’re still trying to figure out just how this will fit into an online world already dominated by numerous social networks, messaging clients, forums, and microblogging services — something that’ll proper render itself more clear as it moves from dev build to public beta. It’s not that we don’t think Wave will be successful — and make no mistake, we are enthused — but calling it “revolutionary” might be setting the bar a bit too high. In the meantime, it’s probably best to pare down those exorbitant expectations while you wait.
(Link: Google Wave dev preview hands-on and impressions)