Pamela Fox's HASTAC presentation, "Lowering the Barriers to Communication" focused on different methods of communication, particularly for collaboration. As an API developer for Google who is currently working on Google Wave, she was a wonderful person to have involved in the conference, since Google Wave has been central to our discussions.
Pamela began her talk by moving through a number of different technologies used for communication, and evaluated them based on the following criteria: editability, number of copies made, structure, history, and notifications of updates. Her presentation moved through evaluations of snail mail, email, discussion boards, and ending with Google Wave. This structure, of course, set up Google Wave as an alternative that provided real-time communication, one central copy, and a flexible structure that allows users to comment on any section of the discussion.
Having used Wave for the first time at this conference, I can see the potential that Pamela discusses. While it is real time, even more so than a chat conversation, Wave can be used synchronously or asynchronously. After I signed up to report on this session, an emergency came up that required me to be in the car during the presentation and discussion time. I can look back, however, and see the record of that conversation as it unfolded, and I can still contribute. What was difficult, though, and was one thing discussed in the Wave conversation, was to fit the different threads of the conversation together. The people who participated sometimes replied to individual sentences within a thread (maybe it’s called a "blip?" I’m not up on my Wave lingo yet.) Because these conversations within a larger blip were quite lengthy, it was difficult to piece together the original blip later. Another possibility discussed was the ability to direct users to specific parts of a wave, using something like a mentions feature. While this is not a current feature, it does seem like a productive one, so people don’t have to skim through the whole wave if it’s not relevant for them.
Pamela primarily discussed various communication technologies in terms of collaborative projects, which is something that I can see Wave being helpful for. It’s been fun to test it out for the conference, which provides us a good model of its capabilities. I wonder about its application beyond project-centered conversation, though. One part of the conversation of Pamela’s talk involved etiquette on online message boards. I wonder if something similar to this would ever replace the message board on websites. I’m interested to see what groups of people end up using Wave, and for what purposes.