There’s an interesting post from David Sklar over at the O’Reilly Weblogs on how he wants to replace email with webfeeds – in particular situations where a company is communicating with him on a regular basis, for example in a billing scenario.
Inevitably there’s a counter-argument – ‘RSS is not the cure for everything‘, for example. And there are also situations where webfeeds simply don’t work.
Tribe.net is one of many YASNS, albeit one of the more popular ones, and in the last week or so it’s launched a redesign of it’s site together with a bunch of new features remixed with some old ones. One of the most popular areas on the site are the discussion forums for each ‘tribe’, so these have been extensively overhauled. Included in the new features are webfeed subscriptions to each forum, so you can now track the conversations in a newsreader.
In principle, it’s a great idea – bring the conversations to the client, rather than the other way around. In practice, it’s virtually useless. Each separate post becomes a separate webfeed item – so instead of a timelined threaded view which allows you to track the conversation from start to finish in the order that the interactions were made, the webfeed delivers the conversation as a series of disjointed messages as and when they’re uttered. It’s like standing in the middle of a room at a party, listening to a number of conversations, but only being able to hear one voice at a time. Instead of following the flow of the conversation back and forward between participants, you’re constantly hopping from conversation to conversation, trying to figure out what’s been said so far and whether you’ve missed the previous interaction that would put the current one into context.
Contrast that with the way in which blogging software such as Wordpress delivers comments as webfeeds – here the entire conversation becomes a single feed rather than interweaving numerous interactions into one. Alternatively the comments become part of the updated post itself, so there is always the context available to refer to. To pick up the thread of the conversation so far, just read from top to bottom and all becomes clear.
To go back to the billing scenario – as it’s not a backward-and-forward conversation, and each iteration or transaction has a consistent syntax, I could see it working quite well as a webfeed. But interactions that require context to be understood don’t lend themselves to a feed situation nearly as well – you can’t break a conversation down to it’s atomic level and still understand it without that context being provided somehow.
It’ll be interesting to see how Tribe takes their experiment forward, but personally I unsubscribed from the forum webfeeds pretty quickly.
