Is wave technology
already in
our hands?

Some interactions that are routine on the Internet or a computer are still missing in Second Life™ (SL). Yet, the amazing range of functionality in SL now seems to anticipate what we see in new web apps like Google Wave. Maybe we already have those capabilities in Second Life™.

This is a long post; but then, I have been hitting it hard for more than two weeks. To prepare for last Saturday’s Wave users’ event I poked around Google’s Wave API documentation, stalked XMPP through a daily reading regiment, and pestered quite a few rezidents with quite a few questions.

In my previous post, I reported some general impressions from hosting that event. Here, I present what I learned in the process about XMPP (the foundation on which Google Wave was built), make mention of a few milestones (both mine and the metaverse’s), and comment on what I see as lacking in SL…hoping to explain the change in perspective alluded to last time.

XMPP—the framework on which Google Wave was built—is an open protocol meant to facilitate near-real-time, extensible instant messaging (IM) and presence-data exchange. Let’s take that one letter at a time; and, in no particular order.

Protocol is a term that refers here to the “rules determining the format and transmission of data” (wordnetweb). XMPP gives us a set of guidelines within which to operate. This sounds a lot like a platfom on which to build; but, my use of terms like “platform” and “integration” does not always integrate with others. Let’s just call ‘em “rules.”

Messaging we are familiar with; we have seen instant messages in Yahoo! Messenger or AOL for years, then mobile text messaging spread, and now there is Twitter. To spot the trail cut by XMPP, remind yourself of the immediacy of these messaging applications, that seemingly instantaneous transfer of text (and text is data).

Presence (or what is referred to sometimes as presence data) has me scratching my head the most. It is said to refer to information about one’s availability. While writing this, I am reminded of something I just read: “Today, there is no central repository of virtual identities that associates email addresses, social network user names, and other identifies with a single real identity” (Maria Korolov, in “Metaplace closing…“). And Wikipedia gives us this:

“[We have] a rich choice of additional presence attributes that can be used for presence information, such as user mood, location, or free text status.”

(Notice one little word in there: “location”. Augmented reality finds purchase here, too.)

And yes, I saved the best for last…

XMPP is an open system; it is eXtensible. Anyone can create new applications by building up from this foundation, this platform, using rules to run their own XMPP server and talk to users on other servers. So, once you see that Google Wave is not the protocol, but just one example of a tool built up from an open framework (XMPP), then you begin to see how anyone can take this framework and create a new sort of “wave” application and host it on their own server (just like you can host your own virtual world, OpenSim).

Oscillating Steam Engine 1
Modelled using Maya
Image by Mark Tomlinson (zcreem)

This next extension raised my eyebrows…it might be new to you, too. Despite the buzz about Wave, the most interesting find in the last few days has been the extension of Maya, the 3D modeling, animation, rendering, and visual effects software. Imagine placing photoshop in Wave, or Qavimator.

Now, there is CoMaya (see video below), a real-time collaboration design tool. Using CoMaya, modelers can work together on the same design even if they are on different continents, seeing each other’s changes in near-real-time.

Yeah…I know! And there’s more…applications like CoWord and CoPowerpoint.

So, let’s sum it up: Where XMPP might let bloggers collaborate on a document in real-time, and CoMaya brings together designers from far apart to fashion a 3D model, we see the crossing of a divide; software bridging gaps in space and time. But, consider this:

That is what is happening every moment in Second Life™.

Right? We already get together to collaborate in the virtual world. We can co-create a document, prepare a slideshow, or create an architectural design by working together; and, everything we do is in real time.

That is how it happened.

Taking a look at another platform opened my eyes. Taking a few steps back helped me to see just how big it is…our Second Life™.

Let’s back up some more.

“…the IETF has formally sanctioned the creation of a working group in the area of virtual world interoperability protocols Virtual World Region Agent Protocol. This is ending of the beginning — or perhaps the ending of the prelude, and the start of a long road.”
—Zero Linden, in an office hours log from October ‘09

Zero Linden’s remarks about interoperability mark a point in time. Whatever principles guided Linden Lab previously, this news points to a wider metaverse…at least it does for Zero Linden. Since it is akin to an opening of doors, interoperability means more; more worlds to explore, more avatars coming ’round, more content to experience.

One day, despite having been totally consumed by XMPP and event planning, I might look back and remember last week for having finally joined the User Experience Interest Group (UXIG). I had been going to the meetings for months, when I could make it; and, I have read many of the chat logs when absent.

At first, I thought the UXIG was a Whine-and-Jeez party (”How come they don’t…” and “Jeez! Why didn’t they…?” and the like). Gradually, I began to see through the (constructive) criticism and sense passion behind the dialog: These are serious users, and many of the rezidents you meet there are serious developers. (It is not uncommon to sit at a meeting with three others who are actually constructing new client viewers, like Imprudence and Meerkat, and some you’ll find in the logs from Zero Linden’s office hours.)

The extension of applications is a strategy that I had not appreciated, up until now. The three-dimensional simulation—the server application that is Second Life™—is more than an environment, it is a platform; a serious developer’s platform. And, it is time for me to treat it with respect; so, it is with all due respect that I ask:

1. Why can’t I drag and drop images for you to see?
2. Why can’t I view any video I want, whenever I want, no matter where I am at?
3. Why can’t I access an archival chat log for group instant messages? (All subsequent conversation is lost to me when I log out or close the group chat panel.)

I have designed a workaround for #1, actually (ad); and, given this new perspective, I have begun to tinker with a solution to #2.

But, in the last two weeks I have come to realize that SL already gives us the means to develop extensibility, implement messaging, and utilize presence data.

We don’t need no stinkin’ Protocol.

We just need to recognize the functional spaces where a new tool would fit, and set upon closing that gap. In some cases, the behavior might be similar to that demonstrated by Google’s Wave.

If we step back, we might see that we are already out in front, and…

Google is waving, at us.

The Second Life Google Wave Users Meet-Up is over and appears to have been a success. A chat log is posted, and edited audio recordings will soon be uploaded. I plan to listen again, first, taking notes this time. Images have been uploaded to Flickr.

My nervousness in the last few days surprised me; this was my first time managing such an event in Second Life. For every item checked off of my planning list, two more tasks had been added. Many things were left undone, some could have been done much better, and—for the moment—I am simply ignoring those that I failed to consider.

Discussion area, Lounge area, and stage and dance floor;
image taken from far away to hide the fact that my
seats were floating. (Click for full size)

I plumb forgot to install a new visual effect created just for the live musical performance. Enough criticism, though, because there is much to celebrate. Rezidents began showing up before midnight (I was still rezzed at the event site; still lining up ducks.), and as many as thirty or more showed up throughout the demonstration and discussion.

In terms of the organization of the event, I had one sure measure of success; it came midway through the discussion. I noticed that I was attending to all manner of administrative tasks; paying very little attention to what was being said. I thought that it would be nice to be able to listen and read what was going on. In other words: I would like to attend an event like this.

Success.

If you have Friendly Fire rocking your sim after an
event, be confident that a good time is had by all.
(Click for full size)

Several advances were made; this post was opened to share these achievements. Firstly, I had a powerful first lesson in virtual world event management…no small thing, I now understand. Next time I throw a party there will be a promoter, probably an event organizer, and I will likely hire out some of the content development. Maybe all of the above. At the very least, I know that my approach will be more confident, my manner emboldened.

Secondly, I learned that my skepticism is well founded in considering the integration of SL with XMPP—or wave technology. One of the reasons for having the discussion was I did not know what I did not know.

1. Is my understanding of the SL simulator and XMPP insufficient so as to leave me ignorant of what is otherwise an obvious opportunity for development?
2. Is there some facility of XMPP that can enhance the file sharing capabilities for my avatar?

I now have an answer to the first question, and few clues to help to track down the second.

Among the rezidents I hear talking about this, none of us describe a compelling scenario in which Wave-SL integration is a benefit. I just do not have a clear idea for extending Google Wave’s messaging and presence into the virtual world. Still, I am considering how Wave can supplement activities in world, supporting a process such as Studio Wikitecture’s collaborative design by providing a new tool for communication and documentation. Most importantly, perhaps, I have entered into a conversation with some who may help me to understand the potential.

As to XMPP file sharing being a boon to virtual world design? Do not look to drag and drop your OpenOffice document onto my avatar soon. But, the discussion has only just begun.

Thirdly, I am seeing the virtual world platform from a higher vantage point. The most encouraging result of the event came as a welcome surprise. The space occupied by virtual worlds such as SL or OpenSim has expanded for me. The boundaries distinguishing these virtual worlds from the larger Internet? They have become a bit more fuzzy. My experience with Google Wave and knowledge of what is “new” about XMPP suggest that more of the web will begin to seep into Second Life, adding even greater depth to that immersion.

The event brought people to an open forum, taught me a valuable lesson, and focused my own study of XMPP and the platform that is Second Life. I am dusting off my wish list, re-visiting features I feel are lacking in the platform. Virtual spaces that might be filled with new content have revealed themselves. In my next post, I will mention several; for each, I have either a solution, something in the works, or an idea worth pursuing.

Comment form is down below.

Eirene Janus and Pia Klaar demonstrated noteworthy patience when they interviewed me for RezLibris, because what I remember is yammering on and on at the slightest prompt. Here, I will share several related links and a few notes made while listening to that podcast. I surely appreciate their interest, and I was glad to learn that RezLibris encourages such a dialog about design.

Much of what made the cut in the podcast referred to the recent Studio Wikitecture project, which I wrote about here and here. Here is a Studio Wikitecture entry describing the challenge.

How can virtual architecture be designed to best serve the needs of teaching and learning in a virtual environment
Keystone Bouchard

Studio Wikitecture presented a unique challenge: There were no client requirements or specifications. The 4.0 project brought together a group of developers who might inform the design process, each one having their own notions about what a virtual classroom should be, based on their experience building in this new medium. And, here is a blog post announcing the final results.

At one point, Eirene asked “Do you think the classroom will be used?” My response (“I am not going to make a prediction” – “I have no notion as to their intentions”) may sound as though I did not care. I was speaking from the perspective that the the project itself was the product, and that it was already a success in my mind (regardless of whether the classroom was used, or not).

Studio Wikitecture is about process. The opportunity to collaborate with developers attracted me. Whether UofA faculty use the classroom or not, I learned plenty; collaboration required communication that was challenging, and scripting techniques and interactive approaches emerged that were new to me.

The “current project” mentioned toward the end of the interview is the iDP Voyager, which has since been released via this RezEd forum.

Thank you, Eirene and Pia, for showing an interest.

I have learned to be optimistic about classes, lectures and seminars; or when approaching anything from tutorials to conferences. I am absolutely optimistic, and it is an “all or nothing” evaluation: If I learn one new thing then the time invested has paid off.

Sure, that is a low bar to jump over; but I said I was being optimistic, not enthusiastic.

Nasus Dumart with guest lecturer, Hiro Pendragon
(image by nasus.dumart)

Hiro Pendragon appeared at Molaskey’s Pub as guest lecturer last night, and he did not let me down. Actually, I learned several helpful bits. According to Hiro:

• educators always pay
• in Second Life “the user is part of a story” (and, in fact, his company “focuses on the storytelling element to drive the whole design”)
• much of their success is due to the fact that they invest “a *LOT* of time researching the technology”

But, the single most striking lesson for me came by way of demonstration…

Recently, I have spent many hours revising the design of an object, the iDP-Voyager, to create a more useful interactive display panel than its predecessor. The project has become one of passion: More features due to changes in LSL since the original version, enhanced usability given a greater understanding of the platform and the users, user-friendly due to a hard-won intention to market objects, and well-documented (of course). This object deletes content to ready itself for your next set or presentation; it speeds up, slows down, even hangs around ’til you’re gone and deletes itself; it slices, it dices…

Crap’s key (image by isfullofcrap)

And then, I am sitting there at Molaskey’s Pub, watching the chat roll by, wondering how Crap winds that key sticking out his back…and Mr. Pendragon rezzes a plywood cube, re-sizes it to an appropriate aspect ratio for images (”This was my first creation in SL…”)…and begins to illustrate his presentation by dragging images from Inventory onto that plywood prim.

No buttons or menus; no dialog boxes or listeners, no lengthy instructional notecard with highly verbose directions including a URL for a wiki support page or email needed. Just sort your pics in a folder, then drag each image onto a prim.

He turned a plain ol’ box into an effective multimedia tool.

It is said that the great ones make it look easy. Well, that was great.

Hexagonal Skybox

Along with making videos and viewing the basic GIMP tutorials, I have recently been building regularly. After two years of working on scripts, primarily, it is good to stretch the platform competencies. But here, I must digress:

Today’s building project (image) reminded me of some poor criticism of Wikipedia that I recently read. I am not a fanatic jumping to the defense of a favorite site, though I am a recovering Wikipediaholic. I often find criticism of the pedia to be well considered. And, as with any social entity, criticism should be tolerated if not indulged. Some criciticism (a recent example) can inform the discussion within the Wikipedia community about the content. No, I am referring to the weak sort of “Wikipedia is lame” comments; as though by simply questioning accuracy or authority you can cast doubt on its utitlity. (Are there some folks who hit the back button at first site of the Wikepedia logo – figuratively thumbing their nose at the site?)

For those who are skeptical about any particular Wikipedia entry:

If you doubt it, keep looking.
If it is wrong, change it.

I typically look for Wikipedia hits in my Google results…which happened again today.

So, how does one make a fairly regular hexagon? Open up your trig notes and start from one side.

Wikipedia works for me.

Having modified two design templates (that just might be implemented!), revised two design documents, submitted a new preliminary proposal, added several small features to a design in progress (Parcel Media Selector), performed minor edits on a video in progress, corresponded with people in four other nations, and completed heavy edits for about a dozen pages across at least four different wikis…I am, once again, wrung out.

I look forward to the demo video showing this game in action:

Household Chores: Broom Breeze By: Wesley Wiebe
The object of the game is to sweep the floor clean of debris.

But, until then, will be happy to come across bits like this (~2min):