All in technology
I've been using SharpReader for the last month of so, primarily because I really like the threading capability. Of course, in that time I have accumulated some thoughts about what could be better / different in the application. This also hints at features I've seen in other aggregators that I'd love brought together.
A number of people are commenting on Microsoft's newly-released SNARF, an extension of their email triage work. SNARF is an Outlook "plugin" that helps one decide how to deal with incoming email.
Stowe Boyd is also thinking about aggregators and doesn't like what he sees. "RSS Readering: Why RSS Readers Are No Good For Me (And You, Too, I Bet)." We share hopes for the future of reading.
Marshall Kirkpatrick gives us a very nice discussion of what he does when teaching RSS (web feeds) to people.
The WearIT@Work project has some beutifully SciFi goals for wearable computing. And they are doing something about it.
I came upon an interesting blog-based discussion rather late, as I have been busy with Thanksgiving and other activities. But when I came upon it, I had a good chunk of the blog discussion right at my fingertips.
Bill Ives wonders "When is a blog, a blog?" based on a talk from Ethan Zuckerman at the Berkman lunch series. Is a blog more than just the technical description of "blog?"
Digital Web Magazine has a great interview published this week with Tony Byrne (by Louis Rosenfeld) on CMS and beyond.
Conventional wisdom is a good guideline, but be sure it makes sense in your circumstances. Inspired by Andy Moore's piece in KMWorld's October supplement on Best Practices in Collaborative Knowledge Sharing.
I'm looking at SharpReader again. Luke Hutteman released a new version (0.9.6.0) this summer, and I am using it again this week. Here are some thoughts about what works well and what doesn't.
efios points to "Identifying Communities of Pracice" from the Shadbolt research group. They have created Ontocopi to parses an ontology to decipher the knowledge networks represented therein.
"What is your 'ideal' feature set for an aggregator (feed reader, RSS reader)?" It needs to stay out of my way, so that I can spend as much or little time reading as I want. Here is a laundry list of things I'd like to see.
Ton Zijlstra has been thinking about his information strategy and focuses on his tools this time. I particularly like that his graphics that show his process.
Frustrated by a term that doesn't seem to mean anything but that all the techies are using? Lee, over at Headshift, gives a decent description of "What is Web 2.0?"
Government Computer News reports that "NARA: New archive system could change records management." NARA has commissioned a new ERA that is to cover all governmental records in all types across all platforms.
I came across Itensil 's Teamlines recently, and it appears to be a good process / project management tool. And I see it as having some components of CCPM as well.
Why not demonstrate "wifi everywhere" in a place where some of the technical infrastructure is already in place, like the airport?
I think the next generation of aggregators / rss readers needs to be better at managing the situation where I have both regular and search subscriptions that bring back the same articles. Here's one idea.