Google Buzz and the fabric of the social web

Google Buzz IconWhen I joined the company a month ago, I was baited with the promise that Google was ready to get serious about the social web.

Yesterday’s launch of Google Buzz and the fledgling Google Buzz API is like a downpayment on what I see as Google’s broader social web ambitions, that have been bubbling beneath the surface for some time. Understand that Buzz is not entirely an end unto itself, but a way for Google to get some skin in the game to promote the use and adoption of different open technologies for the social web.

In fact, I’d argue that Buzz is as much about Google creating a new channel for conversation in a familiar place as it is about how we’re going about building its public developer surfaces. Although today’s Buzz API only offers a real-time read-only activity stream, the goal is to move quickly towards implementing a host of other technologies — most of which should be familiar to readers of this blog.

As Kevin Marks observes, in order to address the mess of the social web that Mike Arrington described, we need widespread use [of common standards] so that we can generalize across sites — and thus enable people to interact and engage across the web , rather than being restricted to any particular silo of activity — which may or may not reflect their true social configuration.

In other words, standards — and in particular social web standards — are the lingua franca that make it possible for uninitiated web services to interact in a consistent manner. When web services use standards to commoditize essential and basic features, it forces them to compete not with user lock-in, but by providing better service, better user experience, or with new functionality and utility. I am an advocate of the open web because I believe the open web leads to increased competition, which in turn affords people better options, and more leverage in the world.

Buzz is both a terrific product, and a great example of how the social web is evolving and becoming truly ubiquitous. Buzz is simply one more stitch in the fabric of the social web.

Designing hashtags for emergency response

I’ve been moved by the devastation wrought by the Haitian earthquake. It’s simply impossible to fathom, with death toll estimates hitting 200,000. In comparison, the Indonesian tsunami of 2004 killed nearly 230,000 people — placing it fourth among the world’s deadliest earthquakes. To give some perspective to those numbers, the atom bomb dropped on Hiroshima in 1945 killed 80,000 people instantly. These are numbers that I simply can’t grasp.

And this disaster still unfolds, with scores pitching in — many turning to the social web and social media to facilitate or amplify their efforts.

Tweak the Tweet logoOne such effort is being lead by Project EPIC, a collection of information scientists, computer scientists and computational linguists at the University of Colorado at Boulder and the University of California, Irvine.

Their initiative, called Tweak the Tweet, provides a dictionary of hashtags for reporting on issues on the ground in Haiti and calling for aid. Here are templates for using their syntax:

Tweak the Tweet

I applaud their efforts and desire to help people communicate their status in a way that facilitates machine-processing. I worry, however, that this approach may limit its success.

Hashtags are metadata for humans first, machines second

The original need for hashtags came from the lack of any formal or public grouping mechanism in Twitter.

For example, when half of Silicon Valley went to SXSW and tweeted for days on end about this speaker or that panel, those who weren’t at the conference desperately wanted some way to filter out such noise. I proposed the hashmark (#) as a way of adding context to a tweet, so that people could choose for themselves to filter out or follow tweets tagged with certain keywords. In July last year, Twitter decided to hyperlink hashtags to their respective search results, and the format became widely adopted — more often than not used to game the trending topics on Twitter’s homepage.

Initially, most people thought hashtags were ugly and useless; even the folks at Twitter thought that they were unnecessary because they’d eventually develop natural language processing algorithms that would supersede the need manual tagging. Contrary to initial complaints about their complexity, hashtags become easier to understand and use with repeated exposure and practice because they are so transparent: if you see someone use a hashtag, you know how to use a hashtag.

And so three years later, hashtags still serve a role in helping people express themselves to each other.

Keep it simple, make it memorable

Language is inherently mutable; mathematics (the language of machines) is not. Verbal language can be adapted by a speaker, and what is heard (or read) is itself interpreted; the conversion is never digital, and invariably bears some loss of meaning.

But using hashtags to clarify meaning prioritizes the needs of the machine over the capabilities of the individual.

Such imposed order in a networked environment can succeed, but only if it achieves instant, widespread adoption, and is itself superficial (that is, it doesn’t require deep knowledge to understand or use the new order). In contrast, simpler, smaller and emergent structures tend to fare better over time, but developing them is not easy (see also: slashtags).

Successful structures should also aim for minimal cognitive burden — by being easy to remember and recall in practice. I’ve frequently seen people tweet about how they “forget to use hashtags” in posts — which is not surprising, since most people don’t think about the metadata of what they say. Hashtags and slashtags are most useful, therefore, when you want to provide additional context that is harder to express otherwise.

Learning from previous efforts

The Tweak the Tweet project introduces a “new order” for using Twitter. Though the words it calls out are mostly common, the use of the hashmark seems gratuitous, given the limited length of the medium (something that Stowe Boyd points out) and that the hashed words comprise the meat of the message, rather than the meta. To give you an example, this is Tweak-the-Tweet formatted post (77 characters):

#haiti #offering #volunteers #translators #loc Florida #contact @FranceGlobal

The same message could be reformatted to be human-readable without any loss of meaning (72 characters):

Offering volunteer translators in Florida. Contact @FranceGlobal. #haiti

While the message may not be as machine-friendly, it may reach a wider (human) audience available to respond to this offer.

Now, I don’t want to dismiss this effort, but instead provide a word of caution on focus. Tweak the Tweet is not the first hashtag pidgin language I’ve seen — and previous efforts struggled to gain adoption and awareness. Perhaps by minimizing the metadata and maximizing the meat, the effort poured into this might achieve a greater effect.

Paving the cowpaths and bulldozing fields

#sandiegofire

Hashtags may never have taken off if it weren’t for Nate Ritter tweeting about the San Diego forest fire in 2007. In fact, his use of the hashtag was the first dedicated use of a hashtag to help coordinate a response to a natural disaster:

Nate Ritter and #sandiegofire

What’s important about his use of hashtags in this case was that he was using them to communicate critical information to people in natural language. His use of the hashtag provided additional context to his followers who weren’t in San Diego, and also modeled a behavior that others could easily emulate when reporting their own news.

When I proposed using #sandiegofire as the hashtag for Nate to use, I first looked at what people were already using the tag their photos of the event on Flickr. At the time, the sandiegofire was one of the trending tags, and that’s how I chose it:

Popular Tags on Flickr Photo Sharing

Had I tried to come up with my own new phrase for the event, Nate’s use of the tag may not have been picked up. #sandiegofire was also better than the alternatives, which were more localized and therefore more obscure to the broader audience. Using “SanDiego” in the tag itself helped bring clarity and context to Nate’s tweets.

Using hashtags effectively means considering the audience and their familiarity with the issue being tweeted about. While tagging lets you be as esoteric as you want, it may limit the reach of your effort, whereas paving the cowpaths means that you build on the familiar and connect with what people already know, reducing friction and inviting contribution.

iList with #ihave and #iwant

iList is an interesting service that originally aimed to take on eBay and Craigslist by leveraging social media. More recently they decided to narrow their efforts to focus on hashtag-based listings and Twitter search. Nonetheless, what I think is interesting about their approach is that it is, on the surface, quite simple.

To use the service, you just tag your tweet with #ihave or #iwant. If you want to get more detailed, you can add your zip code or categories like #forsale or #electronics. But the core service relies on using just two tags which seem to be have moderate usage — proving that getting adoption is always the hard part of any metadata-based communication strategy.

Twitter Vote Report#votereport

The last example is very similar to Tweak the Tweet and was launched by some friends of mine. The Twitter Vote Report project was designed to enable citizens to report on their local voting situation by using a series of hashtags:

  • #[zip code] to indicate the zip code where you’re voting; ex., “#12345?
  • L:[address or city] to drill down to your exact location; ex. “L:1600 Pennsylvania Avenue DC”
  • #machine for machine problems; ex., “#machine broken, using prov. ballot”
  • #reg for registration troubles; ex., “#reg I wasn’t on the rolls”
  • #wait:[minutes] for long lines; ex., “#wait:120 and I’m coming back later”
  • #early if you’re voting before November 4th
  • #good or #bad to give a quick sense of your overall experience
  • #EP[your state] if you have a serious problem and need help from the Election Protection coalition; ex., #EPOH

All tags were optional except the #votereport tag.

They also went through painstaking effort to mobilize people and provide alternative means to participate. They also did a good deal of work to report back their findings in real time (most visualizations appear to be offline) and open sourced their codebase.

They also made sure to make it possible to participate without using Twitter — the hashtags were just a mechanism for getting data into the system.

Design for adoption, stay focused

Around the time it launched, Ethan Zuckerman expressed skepticism about whether Twitter was the appropriate tool for the vote report project, in much the same way I’m wondering whether Tweak the Tweet could take a more focused approach in exchange for wider participation to achieve its goals.

My greatest concern is that there won’t be enough people who can “speak” the “tweaked” syntax, leading to a lot of effort spent building parsers that will be data-starved. While trained volunteers might be able to use this syntax effectively, I wonder if there aren’t alternative approaches that could use the existing corpus of text messages and tweets coming out of Haiti (which probably aren’t geo-coded, unfortunately) to discern the typing patterns that people use naturally in order to facilitate adoption? Perhaps by focusing on fewer tags that are self-evident in their meaning and use, it is possible that this effort could be used to model the proper usage of the tags, making a more direct difference while there’s still time? Unless the audience of this effort is expert users, I’d suggest steering towards simplicity and ease of adoption — and being mindful that typing out a complicated machine-friendly syntax might be the last thing on someone’s mind who’s trying to find or offer help in such a disaster.

Happy birthday to me! I’m joining Google

Google Birthday

Yes friends, I’m turning 29 and I’ve decided to go work for The Man.

;)

In all actuality, I’ve been mulling over such a move for some time, considering a number of compelling opportunities for my next step. After reviewing my options — in light of the progress I’ve made so far and my familiarity and existing relationships with the new team at Google that I’ll be working with — I came to the conclusion that Google offers me the best possible opportunity to continue my work in an environment and culture that is compatible with my outlook, goals, and work habits.

I was trained as a designer, but I’ve been involved with the tech scene since I arrived in Silicon Valley just over five years ago. In some ways, technology has reshaped the way I approach and solve problems — forcing me to think in terms of adoption strategies first, rather than always trying to find the simplest, cleanest design, because of the disadvantaged position I occupied as a non-coder. I can see the consequences of these effects on my approaches first to OAuth, and then to Activity Streams, as well as with OpenID, with positive and negative results. In some ways I’ve had to temper my designer training and put technology first in order to grow an audience. But now I’m ready for new challenges that will expand my ideas and tactics, force me to attack problems from new perspectives, and dip into my design thinking repertoire to operate at a whole new level.

Though I consistently aim high, I want more success in turning my ideas into tangible outcomes, and in doing so, prove the power that I see in open, interoperable standards that can make the web a richer and more intricately spun space.

In some ways, I’m still just getting started with my work.  In joining Google, I see the chance to have a greater impact than I might otherwise on my own. That said, I won’t lose track of what intrinsically motivates me — that I’ve always been about spreading the benefits of the web by creating technology that  fosters innovation and choice. And there’s where I see alignment with what I’ve been doing, and what Google needs to succeed. In fact, my new title at Google? The same one I independently gave myself a year ago: “Open Web Advocate”.

In this role, I’ll still be an active community board member of the OpenID and Open Web Foundations; I hope to help push the Activity Streams project forward with a 1.0 release of the spec soon. And I’m still hopeful about the future of my our semi-neglected and half dormant Diso Project! I’ll also soon be publishing the results of my collaboration with Mozilla Labs, which will provide some insight into what social networking in the browser might look like, and how OpenID Connect might play a role in it.

For good measure, I should also point out that my good friend and colleague Joseph Smarr also made a similar decision recently  — unbeknownst to me at the time! —  and announced that he’ll be joining Google later this month as well.

So, net-net, I’m stoked to be joining The Man Google, and very thankful to have had as much support from the many, many people with whom I’ve connected through the synapses of the social web over these past several years. This is of course a very happy birthday present for me, and I’m eagerly anticipating what’s next for the open social web in 2010…! This can all still be made better. Ready? Begin.

Feel free to leave a comment here, or get in touch via email.

Update: here’s the latest theSocialWeb.tv episode where I make my announcement: