kkfkan wrote:Is it then possible to increase the limited number of items, so that I can retain more older items?
There are two limits at play here.
The first is the one <i>kevotheclone</i> is referring to, how long Awasu will keep content for, and yes, you can configure your channels to keep stuff for as long as you want.
The other one is how many items the publisher is putting in their feeds (I gave 15 as a common value) and since this is something they're doing, we don't have any control over it. The scenario I described, with a feed putting out one new item per hour, means that Awasu will not receive some items at all and in this case, it doesn't matter how long you've asked Awasu to keep content for - if it's never received, it won't make any difference.
Here's another example to maybe clarify things (or confuse them more
). Say you go on holiday for a week and don't run Awasu during that time. Lots of new stories will be published and added to the feed, but as new ones come online, old ones will get removed (in order to keep the most recent 15 in the feed). When you come back and run Awasu again, it will update the channel and get the most recent 15 items, but those hundreds of items that were published while you were away, Awasu will never know about since they've been and gone in the feed. This is a consequence of how RSS was designed. There was an effort a while back to extend it to cover situations like these, where feed readers could ask for historical content, but it never really took off (lack of interest, mostly).