Nice detail: in the article he briefly mentions our Groove/Radio interoptool and uses a screenshot. On his weblog he talks about it some more :
The scenario shown in the screenshot uses Tim Knip's Groove interop tool -- a Radio UserLand add-in based on Groove Web Services -- to create a genuinely new experience of team blogging. Until now, team blogging has meant that a group of folks post to a common weblog. This setup does that too, but it also does something I find much more powerful -- it synchronizes the inputs to the collaborative process, as well as the output. In this case, the input is the combined set of RSS feeds subscribed to by the members of the shared space. Everyone knows that everyone else is seeing the same feeds. Discussion can grow around items in those feeds, and can take various forms: replies to the forum that receives the feeds, IM-style text chat, Roger Wilco-style voice chat.
From an enterprise IT perspective, I realize, the term "team blog" sounds a little vague. So let's nail it down. Those inbound RSS feeds needn't be only internal or external weblogs. They can also deliver customer feedback, system status reports, business intelligence -- you name it. And the output needn't be a weblog that you hope will make the Daypop Top 40. Think of it, instead, as an internal "k-log" that selectively exposes team activity to the larger organization.
Groove Web Services is the enabler here, but I hope we'll soon get over the novelty of that and focus where we should: on finding the right ways to manage context, presence, and attention in all kinds of people- and information-intensive scenarios.
