It’s been pretty quiet here this week. Jan and me had a paper deadline, so I didn’t find the time to blog. I still have a few drafts lying around that I might finish somewhere next week if I find a quiet moment. Time to relax a bit now 
Happy holidays everyone!
I experimented a bit with Jabberwacky today. Jabberwacky is a chatterbot that won the Loebner Prize in 2005 and 2006. It learns from the interactions it has with humans. This sometimes results in funny conversations.
Here is an excerpt of the conversation I had with it:
Me: Hey, don’t be rude, you are the robot, remember?
Bot: You are not a robot?
Me: No. I am a human being.
Bot: You think you’re the center of the world, don’t you?
Me: Well, we humans do indeed.
Bot: What about world domination?
Me: That’s the ultimate goal.
Bot: Does linux mean love?
Me: Linux is the best OS in the world.
Bot: Linux is beautiful.
This is real intelligence people 
I found out a bit too late that Nicolas Nova would be giving a talk at iMAL in Brussels yesterday. Luckily he always puts his slides online
The talk also explained his (seemingly random) blog title: “Pasta&Vinegar”. He states that the hybridization of digital and physical environments is explored both by academic researchers (pasta) and artists and designers (vinegar). In the talk at iMAL he talked about why vinegar is important for pasta
His slides contain lots of interesting and creative ideas, such as blogjects, augmenting animals (e.g. a dog with sensors that controls a WoW character) and a tooth implant that vibrates when you have an incoming call.
If you want to invent something that is to be used 10 years from now, who can you observe? Nicolas states that looking at new media, art and design can give us clues. He also explains that art and design can better convey desire of people for the future, and shows a typical diagram from an IT company that is not appealing to people and too much focused on the technology in the background. He finally refers to the use of technology in art. SIGGRAPH’s Emerging Technologies and Art Gallery are good examples of this and of combining pasta and vinegar.
Just a quick update on my posts about using the IR receiver of the Wiimote for tracking objects. Yesterday I reported on Johnny Lee’s new Wii hack. Earlier, he used the Wiimote to track your fingers and allow you to interact with them.
I just read an article on ZDNet about the ZCam, an infra-red camera that can also track your hands (and is thus pretty similar to Johnny Lee’s technique). The ZCam is developed by the Israeli company 3DV systems. The article on ZDNet explains that the ZCam performs 3D tracking while existing systems like the Playstation’s Eyetoy only tracks in 2D. They also interviewed Bill Gates who apparently was pretty enthusiastic about it
After a bit of googling, I came across a ZCam Beta Program. I submitted a request to join the program, let’s see if I get accepted
Via Hack a day:
Johnny Lee’s back again with his Wiimote interactive whiteboard. Commercial versions of these things are expensive and heavy. His technique doesn’t even need a projector, just a computer, a Wiimote and a simple IR emitting pen. The pen is just a stylus with an infrared LED in the tip.
Johnny Lee is back again indeed I posted about his method to track your fingers using a Wiimote earlier. This time he uses a the Wiimote’s infrared camera to track light pens (pens that emit an infrared light at the tip) on a surface to create an interactive whiteboard. It’s really nice that he can use any surface. You could use a projector in combination with an ordinary projection screen, a wall or a desk. If you don’t have a projector, you could turn any LCD display into a tablet surface.
Since the Wiimote can track up to four different points, these surfaces are also multi-touch. This means you can have multi-touch interaction on any projected image. It would be interesting to combine this with a steerable projector system.
The source code is available. I will definitely keep an eye on his Wii projects page.
Alex pointed me to Evaluating User Interface Systems Research, an article by Dan R. Olsen Jr. that was published at UIST 2007 as part of a panel discussion.
Abstract:The development of user interface systems has languished with the stability of desktop computing. Future systems, however, that are off-the-desktop, nomadic or physical in nature will involve new devices and new software systems for creating interactive applications. Simple usability testing is not adequate for evaluating complex systems. A set of criteria for evaluating new UI systems work is presented.
What I found interesting about this paper is that Olsen tries to address the problem of evaluating UI architectures and toolkits. We assume almost everything in HCI has to be validated by usability tests, while it doesn’t make sense to do so for toolkits and architectures. He proposes a set of alternative evaluation techniques. Olsen knows what he is talking about, as he created the impressive XWeb system.
The paper addresses the question “How should we evaluate new user interface systems so that true progress is being made?”. The author motivates this question by stating that UI systems research (e.g. toolkit or windowing system architecture and design) is still necessary if we want to move beyond the desktop. Lots of good research into input techniques needs better systems models. Multi-user, multi-touch systems are for example often forced into the standard mouse point model, but these systems produce inputs the size of a hand or finger and are used by multiple users at once. Multiple input points and multiple users are discarded when everything is compressed into the mouse/keyboard input model (although multiple users can usually be handled by using multiple mouse cursors). Systems based on one screen, one keyboard and one mouse are the new equivalent of command-line interfaces.
Olsen discusses a few benefits of a good UI systems architecture:
He then goes on to discuss the usability trap. According to Olsen, usability testing has three key assumptions. Toolkit and UI architecture rarely meet these requirements. The first assumption is that users have minimal training (”walk up and use”). It is clear that any toolkit needs expertise in using it. Secondly, to compare systems (or techniques) we assume that there is task that is reasonably similar task between the two systems (”standardized task”). This is also violated by toolkits or UI architectures. Any problem that requires a system architecture or a toolkit is by nature complex and will have many possible paths to a solution. Meaningful comparisons between two tools for a realistic problem are confounded in many ways. Finally, we assume that it must be possible to complete any test in 1-2 hours (”scale of the problem”). Again, this is impossible with toolkits and UI architectures since building a significant application using two different tools would be very costly.
The usability trap is the idea that good HCI research by definition requires usability testing. Olsen clearly shows where usability testing is not suitable and proposes an alternative method to evaluate these systems. He also discusses that searching for “fatal flaws” in a system is devastating for systems research. It is virtually impossible for a small team of researchers to recreate all of the capabilities of existing systems. The omission of an important feature is guaranteed, and the existence of a fatal flaw is a given.
First, Olsen states that we should clearly specify our research in the context of situations, tasks and users (”STU”). He then discusses a few criteria that are useful to evaluate a system innovation, and shows how to demonstrate that the system complies to these criteria. The ones he discusses are:
While I won’t go through all of these criteria, I’ll give a few examples. For instance, importance can be proved through the importance of the user population (”U”), the importance of the tasks (”T”) and the importance of the situations (”S”), e.g. how often do the target users find themselves in these situations and do they need to perform these tasks in those situations?
Expressive match is an estimate of how close the means for expressing design choices are to the problem being solved. It’s a way to reduce the solution viscosity (to reduce the effort required to iterate on many possible solutions). For example, one can express a color in hexadecimal or one can pop up a color picker that displays the color space in various ways and shows the color currently selected. The color picker is a much closer match to the design problem.
Simplifying interconnection comes down to reduce the cost of introducing a new component from N to 1. Suppose we have N components working together. If every component must implement an interconnection with every other component, then the N+1 component must include N interconnections with other pieces. A good interconnection model will reduce the cost of a new component from N to 1. An example would be that every new component must just implement the standard interface, after which it will be integrated with all other components. Olsen gives the example of pipes in UNIX.
Ease of combination illustrates the importance of interconnections to be simple and straightforward. As an example, Olsen refers to the simple HTTP protocol and REST architecture versus the overly complex SOAP protocol. This is no surprise since Olsen based XWeb on the WWW architecture.
It might be interesting to introduce this paper for the course Evaluation of user interfaces to give another perspective on evaluation methods.
I am now using Disqus to handle the comments on my blog. Disqus is a new global blog commenting system. It has a lot of nice features, such as avatars, threaded conversations and global notifications. It allows you to track when a comment you posted got replied to and will in the future even support SMS notifications (hopefully this will work in Belgium as well). The Disqus forum page for this blog can be found at http://intraction.disqus.com/.
They have a simple Wordpress plugin that you can install. I ticked the option “Replace all entries with no comments (including future posts)” to keep my existing comments, and use Disqus for posts without comments. When they have an import system, I will probably import all existing comments into the system as well.
Robert Scoble did an interview with Daniel Ha, the CEO of Disqus.
A few weeks ago I came across a blog post by Cati Vaucelle about Making Things Talk, the new book by Tom Igoe. The book deals with building smart, communicating things. It is built up out of specific projects and uses practical examples to explain different technologies. Tom works at NYU ITC (where Adam Greenfield also works).
Through a series of simple projects, this book teaches you how to get your creations to communicate with one another by forming networks of smart devices that carry on conversations with you and your environment. Whether you need to plug some sensors in your home to the Internet or create a device that can interact wirelessly with other creations, Making Things Talk explains exactly what you need.
The book seemed really useful to me to learn how to build smart things and prototype a ubicomp environment. Unfortunately I was never really exposed to electronics, so this might be a good way to catch up I pointed Kris at the book who ordered a copy afterwards. I had a quick look at it, and I must say it is well-written and fun to read. You need some hardware to really dive in though.
The author uses Processing and Arduino as the basic building blocks. I was pleasantly surprised that the programming environment works perfectly under Mac OS X and GNU/Linux (while it also supports Windows). I would also like to experiment with it at home, for instance to build a remote-controlled mood light Apparently a Wii Nunchuk is also pretty popular for connecting to Arduino as it sports a 3-axis accelerometer, joystick and two buttons for under 20$ and uses the I2C protocol.