Alex and Scott have grown FeedLounge to the point where they have inducted a third wave of alpha users. From the first wave, I welcome you. [Especially Stephen.]
For everyone who’s never used a Web-based aggregator before, I’ve got to talk about polling for a second. No shared aggregator is ever going to be able to poll feeds as often as you’d like them polled. Any shared-services aggregator is going to poll no more often than every thirty minutes, as that seems to be the industry standard that everyone’s come to in terms of how often a feed should be polled by a single resource.
Now, FeedLounge is set up to use an algorithm for its polling schedule that, in my mind, does the job:
- We take the average time between posts for each feed and update the feed at twice that interval. If a feed has a new item every 8 hours, we update the feed every 4 hours. New feeds are updated every 4 hours until the average posting time is determined.
- No feed is updated more often than every 30 minutes.
- No feed is updated less frequently than every 48 hours.
To my way of thinking, that scales better than the way that, presently, BlogLines chooses to update their feeds, polling hourly. Feeds that are updated more frequently—say, Gizmodo—will show new items to you more often. For those high-volume feeds, you’ll actually be fresher than Bloglines.
For feeds that post far less frequently—like, say, GFMorris.com—the polling may only happen every 48 hours. Does this mean that you won’t always be on the bleeding edge with these feed sources? Yes. But when you consider the bandwidth we’re saving FeedLounge is saving, not only on their part but on the part of the independent content producers, we’re doing everyone a favor.
While this might be a letdown for some of you, especially those of you coming from a client-side aggregator where you’re used to feeds being polled on demand, it’s a design decision that simply must be made. Alex and Scott, however, have made a number of other design decisions that are really exciting and just as intelligent as their feed-polling algorithm. Those are the features that I think that you’ll really enjoy.
Any system is going to have tradeoffs and boundary cases. It’s my hope—because I want to see FeedLounge succeed—that you’ll understand and appreciate those tradeoffs and enjoy the service for what it is and what it can become. I know that I’m a very happy FeedLounger; I’ve been using it for six weeks, and I can’t even begin to remember what my old feed-reading workflow was.