Is it just me, or does it seem like Rojo has been getting a little slower on the feed updates? It seems like they’re running into scalability issues as more people add feeds for it to fetch.
Search
Links
Archives
- February 2010
- November 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
What do you mean slow refreashing or slow to parse.
It seems slow on them gathering the feeds into their system; sometimes it takes quite a while for it to pull in new posts and comments to its system.
They probably have an algorythm similar to feedlounge.
They parse feeds that are updated more frequently more and so on. They also most likely set the 30 minute minimum check because they don’t want to be blocked by some of the larger sites that block for checking more then once every thirty minutes.
Ya, that’s what I figured, but I don’t think any of them need to wait 30 minutes. The big sites may only allow one check per 30 minutes, but I doubt that they permanently ban your address for checking more often, so you could just have it keep checking even if it only gets new stuff less frequently from some sites who implement this kind of restriction.
This is one reason why I am still planning to do my own aggregator, because then I will be able to control at a per-feed level how often I want it to be checked.
Actually I know for certain it is because feedlounge went through the same problems with Slashdot and other sites in the begining.
I’ll look for it.
You’re spending more time talking about this vaporware rather then doing it. Why don’t you just work on an existing opensource project?
http://feedlounge.com/support/faq/feedlounge/update-schedule/
Or you could have just checkd the faqs at rojo since it only took me a minute to find this.
Ya, I didn’t want to take the time to look into it.
Slashdot is pretty lame for banning an IP if it checks the feed more than once every 30 minutes. This is what caching is for; maybe they don’t know how to implement it properly.
As for my future project, I’m not spending much time at all talking about it. I’m not aware of any open source feed aggregator projects, but then again, I haven’t really looked much either. One of the reasons why I’d rather just do my own is that I enjoy doing it myself, for the learning and experience, and the satisfaction of having it work exactly the way I want it to. It will take a while to do, once I even start on it, but that doesn’t matter too much to me, since I haven’t promised that I’d have it done by any certain date.