Right. Real-time remote collaboration is novel enough to be able to say that not only interfaces need to be developed for it but also behaviours, etiquette, metaphors -- culture. You could see this with Wave. They were so desperate to hold peoples' attention that they came up with all these new and slightly silly words to help people conceptualise what it was they were suddenly able to 'do'. Too much. Too soon. Too not-for-you-to-determine.

Meanwhile an idea that anyone on the street can easily formulate (shared text editing) is still not widely available in a usable form. It's like promoting the Twitter API and ushering everyone into a new world where everything is a tweet and a tweet is everything, before you have a working tool for personal subscription-based SMS distribution. All these other 'features'... they're not. They're proposed desirable activities. Whether or not they're actually desirable is a cultural development, not a software development. Until people begin to take living, multi-author, simple documents for granted on a large scale, it's really too soon to say if it's a good thing that Bob can embed a sudoku game in the agenda draft or whether a poll and comment thread is a good way to decide where to have coffee or just a bit weird actually.