Answer: When it is missing the point.
Spoiler: This ends up being about the iPad.
Inventing the Future
This I Believe
The relaunch of Wetmachine on newer blogging and serving platforms is a good opportunity to re-introduce myself. I’ve been working on this project — this atttempt to make on-line places where real people can really work together — since October 29, 2004 (and bloging about it since the next day). I write this blog for my children, to read in the future, to show them why I’ve loved going to work each morning.
I want them to know that I believe that right now, we are transitioning from the information age to the imagination age.
In the End
There’s a lot of thunder about Apple’s new developer licensing, in which programmers are required to use one of three members of the “C” family of programming languages. iPhones (and soon iPads) really do matter, so people are sensitive to anyone controlling or wrecking the process by which apps get created. The prevention of developers from using their languages of choice is inflaming an “Apple hates its developers” conception.
I think people are confusing implementation with design.
The Authority
People have been having great pun as this has floated around the ‘net for a while, along with charges of Photoshopping, authentication via reviews of business directories, and charges of racism. Now within a day or so of the release of Gooogle Street View for Hong Kong, no more controversy. (Except for whether or not people should be offended by other people finding the joke offensive.)
Oh. Canada.
Our weekly engineering meeting has a conference table and a huge projection screen. On this Monday, the Vancouver Olympics had just closed, and our three Canadian engineers were celebrating their climactic hockey victory. Being virtual, it was ridiculously easy(*) to find a flag image on Google, drag it in-world, and throw it up on the projector. No mess, no fuss, and no disturbance of the meeting. It might have been an afterthought, but it was appreciated.
In public social virtual worlds, a lot of attention gets paid to avatars — that’s your primary dimension of expression. But in private business worlds, the whole environment is yours to personalize, and it’s easy to change frequently. The discussion referenced in my previous post spoke of spontaneously creating a whole meeting room reserved and named in honor of a visitor.
* Much easier than the mechanics of adding a picture to this blog. See this video, and especially the last minute.
Taking the Red Pill
Under a banner that says “make a difference in the world”, there’s a wonderful piece at active rain about using collaborative virtual worlds for Web 3.0 activity in the real estate industry.
I think we made a difference.
Situation Room
Real situation rooms devote an awful lot to physical requirements.
Here’s a virtual situation room from Forterra’s Olive platform, where there is lot more emphasis on dealing with the situation.
Of course, a real operations center needs to control and interact with the physical world, pulling in not just media, but also manifestations of live data. And the participants must be able to take actions that effect the real world. See an older video of a Teleplace network operations center doing that here.
If virtualization can produce an effective result for much less money, why not apply it in business as well as government? Here’s an example from industry analysts at Think Balm.
Physical situation rooms have costly recording equipment and people to operate them. This is an area where virtual situation rooms can not only be cheaper, but better because easier-to-use means more-likely-to-happen.
Of course, the point of a situation room is to bring experts and stakeholders together to deal with a changing situation. All the participants need to be able to quickly interact with resources, without physical or technological limitation. Unlike the set-in-concrete behemoths, a virtual environment can do better than bunkers to facilitate brainstorming and bringing new ideas together.
Dial Tone
William Gibson has said, “I think in a very real sense cyberspace is the place where a … telephone call takes place.”
David says he thinks of Croquet as the dial tone for Cyberspace.
Sit Down and Shut Up
Impressive Steve Jobs product presentations are built around a unifying theme. Really, the theme of our last version(*) is scalability for large institutions. This is largely architectural work hidden from most users, such as network topology or administrative support.
So far, actual users seem to have been most taken with the manifestation of this theme in the ability to control their colleagues.
*: After prototypes and two commercial versions.
Asset Risk
Julian Lombardi makes some terrific points about asset risk for virtual worlds on his blog. I think the issue is a pretty fertile area for exploration as we all continue to invent new ways of working together, but Blogspot simply doesn’t allow that much content in discussion, so I’ll have to fork it here.
I see the asset risk issue-space as breaking out into at least two dimensions:
* Bit storage vs bit usage
* Point assets vs context
-
This I Believe
The relaunch of Wetmachine on newer blogging and serving platforms is a good opportunity to re-introduce myself. I’ve been working on this project — this atttempt to make on-line places where real people can really work together — since October 29, 2004 (and bloging about it since the next day). I write this blog for my children, to read in the future, to show them why I’ve loved going to work each morning.
I want them to know that I believe that right now, we are transitioning from the information age to the imagination age.
In the End
There’s a lot of thunder about Apple’s new developer licensing, in which programmers are required to use one of three members of the “C” family of programming languages. iPhones (and soon iPads) really do matter, so people are sensitive to anyone controlling or wrecking the process by which apps get created. The prevention of developers from using their languages of choice is inflaming an “Apple hates its developers” conception.
I think people are confusing implementation with design.
The Authority
People have been having great pun as this has floated around the ‘net for a while, along with charges of Photoshopping, authentication via reviews of business directories, and charges of racism. Now within a day or so of the release of Gooogle Street View for Hong Kong, no more controversy. (Except for whether or not people should be offended by other people finding the joke offensive.)
Oh. Canada.
Our weekly engineering meeting has a conference table and a huge projection screen. On this Monday, the Vancouver Olympics had just closed, and our three Canadian engineers were celebrating their climactic hockey victory. Being virtual, it was ridiculously easy(*) to find a flag image on Google, drag it in-world, and throw it up on the projector. No mess, no fuss, and no disturbance of the meeting. It might have been an afterthought, but it was appreciated.
In public social virtual worlds, a lot of attention gets paid to avatars — that’s your primary dimension of expression. But in private business worlds, the whole environment is yours to personalize, and it’s easy to change frequently. The discussion referenced in my previous post spoke of spontaneously creating a whole meeting room reserved and named in honor of a visitor.
* Much easier than the mechanics of adding a picture to this blog. See this video, and especially the last minute.
Taking the Red Pill
Under a banner that says “make a difference in the world”, there’s a wonderful piece at active rain about using collaborative virtual worlds for Web 3.0 activity in the real estate industry.
I think we made a difference.
Situation Room
Real situation rooms devote an awful lot to physical requirements.
Here’s a virtual situation room from Forterra’s Olive platform, where there is lot more emphasis on dealing with the situation.
Of course, a real operations center needs to control and interact with the physical world, pulling in not just media, but also manifestations of live data. And the participants must be able to take actions that effect the real world. See an older video of a Teleplace network operations center doing that here.
If virtualization can produce an effective result for much less money, why not apply it in business as well as government? Here’s an example from industry analysts at Think Balm.
Physical situation rooms have costly recording equipment and people to operate them. This is an area where virtual situation rooms can not only be cheaper, but better because easier-to-use means more-likely-to-happen.
Of course, the point of a situation room is to bring experts and stakeholders together to deal with a changing situation. All the participants need to be able to quickly interact with resources, without physical or technological limitation. Unlike the set-in-concrete behemoths, a virtual environment can do better than bunkers to facilitate brainstorming and bringing new ideas together.
Dial Tone
William Gibson has said, “I think in a very real sense cyberspace is the place where a … telephone call takes place.”
David says he thinks of Croquet as the dial tone for Cyberspace.
Sit Down and Shut Up
Impressive Steve Jobs product presentations are built around a unifying theme. Really, the theme of our last version(*) is scalability for large institutions. This is largely architectural work hidden from most users, such as network topology or administrative support.
So far, actual users seem to have been most taken with the manifestation of this theme in the ability to control their colleagues.
*: After prototypes and two commercial versions.
Asset Risk
Julian Lombardi makes some terrific points about asset risk for virtual worlds on his blog. I think the issue is a pretty fertile area for exploration as we all continue to invent new ways of working together, but Blogspot simply doesn’t allow that much content in discussion, so I’ll have to fork it here.
I see the asset risk issue-space as breaking out into at least two dimensions:
* Bit storage vs bit usage
* Point assets vs context