Drinking from the firehose

Some firehoses to drink read from, other than twitter’s:

  1. Google Buzz, through their activity firehose API methods;
  2. FriendFeed, using their real-time updates methods.

While the first works via pubsubhubhub, the second uses a combination of long polling and a cursor that helps you make subsequent calls.

More on the @replies subject

I just stumbled on a Buzz by DeWitt Clinton about a possible solution to the use of decentralized @replies. From the Buzz:

I want to throw some ideas out there about how it can someday be done in a decentralized fashion using open technologies such as WebFinger, Portable Contacts, AtomPub, and Activity Streams. (And maybe Salmon. Read on.)

The proposal would let you address any user of any application in a complete decentralized way.

And not only is this process fully decentralized (i.e., there doesn’t need to be a Google in the middle), it delegates very well, so that domain owners wouldn’t have to implement it themselves — but they could later if they wanted to.

On the use of the @ syntax by Google Buzz

Just a quick note to archive the way Google Buzz is using the @ syntax. From “Google Buzz Tips“:

If you’d like to send a private message to someone, type @ and use Gmail’s autocomplete feature to find the email address of your contact.

In practice, you address other users by typing an @ symbol followed by their e-mail address, like @user@example.com. This is exactly what I proposed a while ago as an easy way to address any user on any Web application:

Afterthought question: can this microsyntax be expanded to @user@application so that we can finally address any user on any Web application easily. I’m thinking about that.

For now, you can only send messages to other Google Buzz users but I’d expect this syntax to be used to address users of other supported destinations (twitter et al).