Google Wave is "wow"

Google Wave is one of the most exciting products I've seen in a while -- it could reshape how we work, how we collaborate and how we do business. This is big. Provides me a ton of inspiration for Drupal ...


Per André Rønsen (not verified):

I was waiting for this response :) Very lovable!

May 29, 2009
Stefaan Ponnet (not verified):

This reminds me of the concepts of Dan Bernsteins 'Internet Mail 2000' ( ) implemented on top of 2009 web technology.
Impressive indeed!

May 29, 2009
Olivier Biot (not verified):

Apparently Google Wave is being hyped as "the" future of massive collaborative online communication. Pretty disruptive vision!

May 29, 2009
@DavidWheelerPhD (not verified):

Drupal Developers, get started with the API

This link tells a little about the origins of Google Wave.

May 29, 2009
Nick Vidal (not verified):

It's coming to Drupal, but much better!

May 29, 2009
Jeff Noyes (not verified):

Very cool. Its like a clash of Twitter, Facebook, blogging, instant messaging, and Google docs. Now I really wish I bought Google's stock at the opening price of $85USD.

I can see how this would make progress on building Drupal that much better/faster. At present, it's a challenge to stay in the loop and decipher between what's new, old or most relevant.

Seems pretty important to start Drupal integration on this ASAP. Glad to see David Wheeler already on top of this.

May 29, 2009
momendo (not verified):

Thinking in terms of Drupal.

This validates some concepts that exist in Drupal 7.

- Everything is a field. No need for nodes.
- Comments are fields. No need for special cases other than relationship.
- RDF/XML/RSS to transparently share data, pulling in data, pushing data out as widgets and raw data
- Drag & drop is good UI
- Inline editing is good UI
- WYSIWYG editors is good UI, D7 hasn't decided on this yet.. :-(
- Realtime interaction is helpful
- Revisioning, tracking changes, merging, playback are key to collaboration
- Intuitive spell checker and translation helps communicate better
- Extensions/plugins are key to extending features
- Opensource FTW

May 29, 2009
Gábor Hojtsy (not verified):

Sarcasm on: If the only thing people understand from Wave is that threaded commenting is good, then Google helped us being perceived as more user friendly :)

June 2, 2009
jackinloadup (not verified):

I think a new drupal group is in order to encourage collaboration about how this will affect the community.

May 30, 2009
David Oster (not verified):

This is huge!!! This changes a lot the way people will collaborate!!! Where Drupal stands in terms of these advancements though? We will see.

June 2, 2009
Gregg L. DesElms (not verified):

Thinking of Wave in terms of "replacing" such as GMAIL (or even email, itself) is just silly. Not every Internet communication needs to be (or even should be) as would be in Wave. Traditional email, at the very least, should (and likely will) never go away. Of this, I think there should be little fear or doubt.

Now, that doesn't mean there won't be a place -- and a potent one, indeed -- in our lives for such as Wave and its ineluctable variants. It, too, will be useful, under the right circumstances. In fact, from my admittedly only-cursory analysis of it to date, I'm thinking that what actually MAY be "replaced" by Wave, as a practical matter, is traditional "chat," as we now know it (though traditional chat, mark my words, will continue to be around for years and years, too, no matter how good Wave ultimately gets).

Regardless, one thing about which we should all be clear in our minds is that we're not talking about the mere replacing of anything, here. Wave, for better or worse, seems very nearly of the nature of paradigm shift... and far be it from me to suggest that that's, necessarily, a bad thing, here.

It does, however, come with pitfalls about which we should all be watchful, if not actually downright concerned. For example, though it's now coming out in articles (and/or rebuttals to such as I am posting here) that it's likely to be user-configurable, initial writings about Wave touted the ability (and represented it as essential to Wave's very way of operating) of all persons in a "wave" (or a thread) to be able to see, in real time, all others' keystrokes, as they type.

Let me repeat the salient words of that, here: AS. THEY. TYPE.

Think about that, please, for just a moment. It's a far larger problem than, perhaps, it initially seems. Like how sausage is made (or, as some joke, like how laws are passed), some things in life may better be left something of a mystery to those who ultimately consume (or are regulated by) them; and, most importantly, solely at the creator's option.

The ultimate impact and meaning to the reader of anything written would be inordinately influenced by said reader's having been a witness to its creation. If one is a thoughtful writer who doesn't just blurt out every wayward thing which flits through one's brain, then one is going to pause to think while one types, and back-up and delete and re-type, and whatever else behind-the-scenes activity goes into what ends-up being the finished written product. If the reader were able to witness what the writer merely paused before writing; or actually did write, but then thought better of and either removed or changed to something else, then the bell of what the reader saw along the way cannot be un-rung; and the reader's ultimate interpretation and understanding of the final written result will be indelibly affected in ways (even if not immediately obvious) more likely than not to be inherently bad for all concerned.

Now, if it's true, as some who challenge such as my assertions, here, are now saying, that the ability of others to view one's keystrokes as one makes them is (or at least will be) user-configurable in the version of Wave which is finally released to the end-user wild, then my concern, at least on this particular privacy-related point, is happily ameliorated.

However, of larger philosophical concern to me is that the creators of Wave apparently believed, even if only briefly, that something as basic as this issue would not be important. What, then (if anything), does that mean we should also be wary of in the realm of personal privacy protections, just generally, for users of this new and groundbreaking product? For what else should we be watching which may, ultimately, negatively impact us because of fundamental, and at least initially seemingly harmless, privacy encroachments...

...encroachments which may not even be recognizable as encroachments to Wave's creators because, perhaps, of their nationality and upbringing (nothing negative, mind you, intended by that wording, I assure).

One potentially troubling impact (at least from the standpoint of Americans, in my opinion) of globalization (which, incidentaly, I'm not fundamentally against, despite how what I'm about to write may make it seem) is how the sensibilities of those non-Americans who create things which all others on the planet end-up using can unintentionally contravene that which Americans hold perhaps nearer and dearer to their hearts than do non-American others. Those who grew up and still live in countries where such things as privacy and freedom of speech are not as absolute and paramount as in the US may or may not necessarily value such rights to the same degree as do Americans; and it sometimes shows in their work.

It has not escaped my notice that the two brothers -- brilliant though they are -- who created and continue to develop Wave were neither born and raised in, nor now live in, the US... and so I fear (and I may be completely wrong about this, I realize... but absent, at this point, any reason not to, I am nevertheless fearing that they) may not place as much of a premium on the notion of absolute privacy (if desired by the end-user of Wave) as do Americans.

Or, who knows, maybe they do. I don't know them, and it's unfair of me to presume, I suppose (or even to suppose, I presume). One way or the other, though, it should be at least a concern to all that the default behavior of Wave seems so inherently and joltingly privacy-denuding.

So, then, again, begged is the question: Of what else (if anything), in Wave, should we who hold inviolate our privacy be wary?

To appeal to (at least thinking) Americans, the makers of Wave need to take steps to ensure that if the end-user wants to protect his/her absolute privacy while using this admittedly exciting and paradigm-shifting new product, it can, via easy configuration settings, be satisfactorily and incontrovertibly achieved at all possible levels, and in all possible ways. Moreover, as it is developed, the makers of Wave might need to realize that they may, because of their nationality and upbringing, not necessarily even recognize what all of those levels and ways might be; and the Americans (or even the non-Americans who at least fully grasp the American viewpoint regarding all this) who work on the development of Wave should ensure that no privacy holes such as I'm discussing here remain anywhere in it when it's finally and fully released into the end-user wild.

Or so it is my opinion... my two cents worth, as it were...

...which my ex-wife, for example, among others, has been known to quickly attest tends to be about all it's usually worth.

Gregg L. DesElms
Napa, California

June 3, 2009
SHL (not verified):

Was looking for the place where Drupal/Google wave discussion happens, and found it here at last.

I was looking in the Google wave drupal group first with no luck, but let me crosslink:

June 10, 2009
SHL (not verified):

Ooops, now I see the group was linked to already.

June 10, 2009
Thure Bergström (not verified):

Agree. Google Waves is big.
From a collaboration standpoint the biggest change I have seen for 30 years. (Since e-mail came about in the late 70's.)
I have one question.

In the waves demo you can see how a user 'owns' his data (can be any element in a wave) and publish it as private, shared with someone(s), shared with group(s),public.

That means that a user can use a wave as the full documentation of a communication subject, which is a major productivity advantage. Combined with the playback functionality it's a killer.

So far I have seen Drupal as a publishing system, where the ownership of a node comes with an editor role. That makes Drupal less usable as a collaboration/documentaion platform. From an user point of view.
Is there any way to merry these two concepts. The bottom up access rights of a collaboration platform like Waves (and Notes and many document systems) and the top down editor model I have seen so far in Drupal?
That would be great - for shure.

October 2, 2009


Updates from Dries straight to your mailbox