Way behind on feed reading
Tuesday, October 3rd 2006.Do you see that (1052) next to Cooking on the picture above? That’s how many unread posts I have in my cooking-related RSS feeds. Yeah, go figure! I probably have too many of those feeds in my list, as you can see if you click on the image. Still, it just means that my current work schedule (and some occasional but necessary relaxingofcourse…) is keeping me from reading the stuff that really interest me. Usually, I’m pretty good at keeping that number close to zero, but lately I’ve only been able to do that with my other (non-cooking related) feeds.
I use the bloglines web based reader to read my feeds. I absolutely love the service and the simplicity of this reader. Unfortunately, once I get in a state of behindness (for lack of a better word) such as you can see on the left, there is really no clean way to catch up. Once you click a feed, you are presented with all the unread messages and they are all immediately flagged read at that point. You can mark them all as unread again, or even individually, but what I’d really like is that I can mark them read individually.
The problem with this approach is ofcourse that I wouldn’t want this to be the default behavior, because having to flag messages as read manually would severely slow down my normal daily reading. I’d like to ask the bloglines team for a better way to handle this, but I have no clean solutions to propose. Any ideas, anyone?
In the meantime, I hope I’ll find the time to catch up, but the way my schedule is looking now, it looks like I’m going to have to press the ol’ “Mark all as read” button soon. That thought just makes me shiver…
2 Responses to “Way behind on feed reading”
Leave a Reply
Search
Related Entries
- No related posts

Google reader does it right!
I used bloglines last year, but then I stopped at the end of the semester and hadn’t gotten back into it until recently. But then I decided that I should shop around, since bloglines is nice, but leaves a few things to be desired. And frames are sooooo 1997.
You should have seen how many unread items I had after 5 months of not reading…
Anyway, the new Google reader (the first release sucked) solves the read/unread problem pretty well: it serves up the stories in a list of headlines, and you navigate them javascript-style with j and k. When an item is “highlighted”, it expands and reveals the body of the story.
I’m not suggesting that you switch to Google Reader, but this AJAX-type solution is pretty nice.
I recently heard about the Google reader update. I too tried its first version out once, and it sucked. Maybe I should check it out again, you’re not the only one to say good things about its recent changes.
Ofcourse, bloglines also has nifty ‘j’/'k’ vim-style navigation, and many other shortcuts. It’s had them for a while now, also with nifty AJAX scrolling