Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Solving feed overload

Freshness Warning
This blog post is over 17 years old. It's possible that the information you read below isn't current and the links no longer work.

Ilya Grigorik has some thoughts on how to solve the information overload that often comes with feed reading. If you subscribe to hundreds of feeds, how do you find the interesting stuff without reading everything? How do you separate the signal from the noise.

Keyword filtering is one common approach. But there’s some significant problems.

I use keyword monitoring to let me know on new product announcements and to track public mentions of certain people or products. It does work in that instance. However, the act of me specifying the keyword presupposes a priori knowledge of the topic I would like to track. The reason why I cast my net so wide across so many sources is exactly because I don’t know what I’m looking for - I just want to make sure that once something significant happens, I’ll know about it! Not only does keyword filtering fail here, but the act of choosing the keywords is extremely hard in itself.

To some extent, feed readers appear to try and justify their existence (and boost their usage) by recommending feeds to watch. (Note that we’re sometimes guilty of this at Feed Crier, too) Suggesting additional feeds to read based on what you’re already reading is only contributing to the problem. Ilya rightly takes we feed reader developers to task, asking us why our suggestions are so self-serving, when we should be helping our users.

One approach that Ilya rejects is allowing our friends to decide what I read and what I see. He suggests that doing so places a burden on them and only works if we’re using the same system anyway. I’ve found that this is not the case, but only when looked at from a slightly different angle.

Before we descended into the echo chamber, blogs were a log of interesting places on the web. That’s the root of the term even: web log. The early blogs were human filters for the vast web. People chronicled their daily journey through the intarwebs, leaving breadcrumbs for others to follow. Almost three years ago I suggested that enterprise blogging could perform the same function for intranets by allowing employee blogs to act as human filters for the most important things.

Human filtering can work. I started subscribing to Roland Tanglao’s blog several years ago because he was an effective filter for high-output bloggers like Dave Winer and Robert Scoble. He separated the signal from the noise—if something interesting was said on a vast number of blogs, I could count on Roland to reblog it for me. His blog as since morphed into his personal interests, but there are other bloggers that do the same things.

Ilya suggests two approaches, building smarter feed readers and an interestingness measure that comes from the community.

Shifting the burden on the RSS reader could yield some improvements. Clustering, correlation, prior reading patterns can all be taken into account when information is sifted through the filters.

He recognizes the problem with a smart reader—that it takes a fair amount of training to start doing it’s job. A reader needs to watch your habits and learn what you find interesting, something that takes time. My friends at Touchstone are working on solving the problem in part by passively watching what you do on your computer and using that information for training. This passive approach can ease the training burden. Training in this case doesn’t require you to do anything different than what you are already doing. Their attention engine looks at what you’re already paying attention to and helps you find other things that you’d find interesting.

A community interestingness measure is what memetrackers are working on. Tailrank, Techmeme, and others (disclosure: I’m an advisor to Tailrank) are using the linking patterns of blogs to determine what the community at large finds interesting. Tailrank takes this a step farther by helping you find the interesting things in the feeds you’re already reading. Their My Tail service allows you to tell them what blogs you’re reading and get a customized page and feed of the most interesting items in those blogs. And the clustering behavior of memetrackers can help readers find related topics and other points of view.

I have a nagging concern, however, that these systems designed to reduce information overload could reduce serendipitous findings as well. If all you see is things that you already find interesting, how do you expand your horizons? By reading a vast and eclectic collection of feeds, I’ve been exposed to new and interesting ideas—ideas that I wouldn’t have even known I’d have liked. Will attempts to reduce information overload contribute to creating a monoculture?

Dave Kaufman - Techlife
December 22, 2006 10:31 AM

2 things... 1 - I am still waiting for the FC update I asked for when it opened for biz....the "youtube bar" - most popular, most subscribed, most viewed, newest feeds, staff picks, etc. You get that. 2 - Based on your article, the second half...I think a TiVo suggested viewing/reading is what they seems to be proposing. Makes sense, but only if they have an API. No offense to them, but I want my reader (FC of course!) to see what I am reading, see what others like me are reading, see the keywords from the posts of all of us and suggest single posts to view. Loyalty is a bitch I guess. And yes the new tagline for FeedCrier should be, "You had me at Hello."

Chris Saad
December 22, 2006 5:24 PM

Thanks for the mention my friend :) Just to clarify - Touchstone can actually, if you give it permission, index your hard disk (including documents, IM chats, browser history etc) to create an instant and ongoing snapshot of your interests - no handshake period. And because we scan a broader range of content than just your interactions with OUR application, we are less prone to making the wrong assumptions (we have all heard about the Tivo assuming it's user was gay because he watched Queer Eye for a Straight Guy once). Also I agree that serendipity starts to fade, but at Touchstone we focus on one problem and one problem only - escalating alerts. This means you get alerted about important stuff to your life in proportion to its importance. If it’s important, then it can rout it to FeedCirer for IM Alerting. It's a PERSONAL Attention Manager. If you want serendipity then we suggest you ALSO use a Popularity Engine as well like Digg or Techmeme etc.

Yoz
December 25, 2006 12:50 AM

I'm also a big believer in human filtering; en masse, I think it's a great self-balancing system. Some people are great for finding stuff that (a) I find interesting and (b) I haven't seen. I usually end up finding these people through others' "via" links. While putting more smarts into feed readers could help, the things I'd most like to see are the dumber-but-faster tools like Reblog being built into the more popular feed readers.

This discussion has been closed.

Recently Written

Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.