Comments: Phil Wolfe Comment

being someone who studies blogging academically, this raises a few questions:

- What do you do with blogs, etc. that don't publish feeds or publish partial posts to their feeds?

- How much is the use of your reader reading and how much is it searching?

- I've always wondered why some people had reading lists (to distinguish from publicly-displayed blogrolls) with more than 100 blogs. Certainly, they must have a hard time keeping up with all that reading! Phil's comment above lends me to ask: So it's not as if you read all of the blogs on your reading list, but you read some regularly and just keep the rest around as "data", right? (for whatever purpose you may use it for as a power-blogger)

- What causes you to move a blog from your "regular reading" list to the "just saving for data" list? If you don't distinguish between these categories, how to you manage to read all those damn blogs? Do you do an implicit categorization / prioritization (that is, skip over the NYT's front page, 'cause you know a story will come through other blogs with commentary)?

Posted by joe at December 19, 2004 11:52 AM

Really, what's the point? 1000 feeds!? You're obviously not reading 1,000 feeds worth of posts everyday, so you're just downloading them for (a) fun? (b) research? (c) to bog down as many servers as possible so you can be proud of the large amount of feeds you subscribe to (and reload every hour?)??

I just don't understand people sometimes... RSS wasn't meant for people to just download as much sh*t as possible to their computer and keep it all organized. You need something far more powerful for that. Like Google.

News articles always exist in archives, and have for 100 years. Be more selective with your feeds and stop hogging the servers' bandwidth. There's few people who have a legitimate reason for use of 1,000 feeds. Few. Very few. That's just abuse of the technology.

Posted by Aszhat at December 19, 2004 01:31 PM

I hope my original comment about the common RSS "use case" didn't come across as a scolding.

Phil's right that we should (and I do) support Mary's wish to have RSS reader software work for her the way she wants to use it.

But, this wish is different than assuming or expecting that software features that might be commonly dependable in the future should have been so yesterday. (So, that's specifically in regards to Phil's comment.)

The main point about the RSS use case is that, it's important to fact-check any assumptions one may have about what RSS readers are really built to do well.

This is because, in particular, there is a lot of enthusiasm around RSS and what it does (as Phil's comment shows!). And, along with that enthusiasm comes wishful thinking and tolerance for things that don't work too well, but folks are positive about (and even endorse) because they suggest better things to come.

As a somewhat tangental analogy, I've seen several companies buy $100k+ software products that completely failed to meet their core needs. They bought those things based on enthusiasm within their "echo chamber" of decision making, where enthusiastic voices drowned-out more skeptical ones.

Posted by Jay Fienberg at December 19, 2004 03:43 PM