Notes:

  • My "participatory deliberation" is elemental. Therefore it is platform and presentation agnostic. Also: my analog to the "wave" object is refered to as "bead", allusion to Herman Hesse's "Magister Ludi" aka "Glass Bead Game Master".
    This all matters when it comes to access / indexing / discoverability:
    CNET Editor Rafe Needleman in "Debating the power of Google's Wave": "It's fun to play with now, but we don't know what using Wave will be like once we start getting overflowing inboxes of waves."
  • Pro-tension: "Information wants to sprout"

Notes from Google Wave Developer Preview at Google I/O 2009 (see Wave - Under the Hood for follow up):

  • 9:43 "Instruct the server to split the message"; better: like TBuzz and Blog!, create a smart spawn by blocking text and then striking Reply. The primitive is to quote/cite text; more elegant would be a) an anchor and b) a mouse-over style text block.
  • Re: email-type conversations and IM-type conversations no longer require 2 tools; this recognizes the cognitive modalilties involved.
  • 12:43 The problem of bringing someone in post branching i.e. loss of context. The solution is the conversation object i.e. the entire wave can be accessed via "playback". (Playback animation comes with a time-line slider; does this make threads re-entrant? break out of the temporal silo?)
    NB1: Sub-trees of the object can be access restriced.
    NB2: Messages that were edited by another are displayed c/w markup to those who received the original. (Edits push the message into the Inbox as unread.) Current version can be dragged to produce a fresh wave. (Merging subsequent edits in the original? Seems problematic. "Different teams working on different parts of the wave and then ..." 33:45)
  • "Private Messages" (PMs/DMs) => "Private Replies". see NB1.
  • NB2: HTML 5 does not yet support images Drag&Drop; that is the only part of Wave that requires Gears.
  • "You get a lot of waves so you need a way to organize them" i.e. tags. 40:00 (Dragging a wave from the list into an open wave creates a link.)
  • Extensions 43:00
  • "Bean Soup" = language model; check meaning from context FTW (Red underline for suggestions is shown to all participants.) 45:00 Linky: 45:45
  • "Any open social gadget can sit inside a wave."
  • "Yes/No/Maybe" gadget 50:00
  • Chess c/w replay 53:00 ... create Go?
  • GMaps - Collaborative interaction 53:00
  • "Store updates to the state in XML then ..." 53:50
  • Extending to integrate external e.g. Twitter 57:00
  • "Tweetie" can update Tweet searches as though alerts. 1:01:00
  • Extending into existing work-flows. 1:01:50
  • Post to bug-tracker (commented lofted to ticket) c/w inline reply function (streamed to ticket; updated ticket would ramify to wave).
  • Federation 1:05:30
  • Acme Wave and Initech Wave (Telnet?!)




  • "An HTML 5 app built using GWT." "Collaborative document production tool c/w extendable content model." (34:15) Real-time collaborative editing; see 35:00

    NB: I suggest that the name "Wave" can be best understanding after priming with the term "meme". Our taxonomy is weak here; is email an activity? a process? a core function? Is "buying" an activity? Is "search" a function?
    My notion is that Wave allows communications and collaboration along threads ... and those threads, packets or constellation of meaning, can be thought of as waves. Viz.:

    "At its core, Wave lets people create a document to which multiple users can add rich text, multimedia, gadget applications and feeds, and do so concurrently in the way in which people interact on, say, instant messaging. These "waves" can be rolled back to view the evolution of the document."
    --"Update: Google's Wave consolidates core online features into one tool" (ComputerWorld.com)

    "Gmail can collate related messages into conversations or threads" (see Lars Rasmusen on I/O video 6:20), i.e. waves.

    "Waves starts out with the definition of a conversation which is a light-weight tree-structure of messages and a set of users participating in that conversation. ... We think of the entire conversation object as being a shared object hosted on a server somewhere and users that participate can open up that wave, leave their replies, go away, and then when the next user comes she can open up that same shared object, see those replies and add her own. That's how the wave grows, that's how the conversation builds up. This is a model of how bulletin boards work."
    "This being a hosted conversation it's easier to keep track of structure." (Stephanie; 9:15)



    My first glimpses of the interface (see screenshot; more at "Forget Google Apps: Google Wave is the New Epicenter of the Google-Microsoft War") made me think of something I've adopted almost as a motto: "somewhere between boredom and helmet-fire". (see "Between speed and being interrupted too often." 43:00) Is Wave Bloatware" at Technologizer.com highlights that point:

    "Among the many interesting questions about Wave is this: Is it bloatware? It's not ready for release yet, and it appears to already be bursting at the seams with functionality. Screenshots show a service that crams dozens of features, options, and snippets of information onto the screen -- less an example of Google-esque minimalism and more like a Microsoft app that's been through a few versions and is shoehorning stuff in."
    In his Gigaom post Jordan Golson comments, "Wave could be a competitor to Outlook and Office if Google were to roll Docs/Gmail/Cal under the Wave umbrella."

    skh.wave.io@gmail.com

Google Wave will be available later this year.

Check out the developer preview at Google I/O 2009

Google Wave is a new tool for communication and collaboration on the web, coming later this year. Watch the demo video below, sign up for updates and learn more about how to develop with Google Wave.

Learn
Google Wave can make you more productive even when you're having fun.
Take a sneak peek.

Develop
Learn how to put waves in your site and build wave extensions with the Google Wave APIs.
Visit code.google.com/apis/wave.

Build
Google Wave uses an open protocol, so anyone can build their own wave system.
Learn more at www.waveprotocol.org.


Links

  • About Google Wave
  • Google I/O - Sessions
  • Google Wave API - Google Code; Google Wave API at Google Groups
  • Google Wave Drips With Ambition. A New Communication Platform For A New Web.
  • Update: Google's Wave consolidates core online features into one tool
  • Introduction - Google Wave Federation Protocol
  • Went Walkabout. Brought back Google Wave.
  • Googlegram
  • Meet the Google Wave Team
  • Google Wave Developer Preview at Google I/O 2009
  • Blog posts and Articles

  • Xooglers
  • this page on Sites at google
  • "google i/o keynote" +wave - Google Search
  • "Lars Rasmussen" - Google Search
  •   |   notes   |   comments   |   resources   |