Version: 1.0-beta7 "Lippel" (using KDE 3.3.1, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-2) OS: Linux (i686) release 2.6.8.1-kanotix-5 Some feeds (e.g. Slashdot) amount of times you can fetch a feed within a time. If you do not comply you are blocked for a time, which is enoying. To prevent this, you can put seeting in a way that you comply to that policy, but if for example you restart computer or use a fetch all, you don't comply with this policy because the feed is fetched again. What I would like to have is a seeting for singular feeds, that prevents me from fetching a feed more often than allowed by blocking it fetching more often than in set timeframe.
There was a bug in interval fetching which caused that all feeds were fetched one minute after the start of akregator. This is fixed now, akregator remembers the last fetch time. The only way to fetch more often than specified in the interval is pressing "Fetch" or "Fetch All" manually (And, if the feed is not available, akregator retries every minute). Do you think such a "fetch prevention" is necessary for manual fetch actions or does the new interval fetch behaviour fit your needs?
> Do you think such a "fetch prevention" is necessary for manual fetch actions > or does the new interval fetch behaviour fit your needs? I think it would be still useful.
I disagree. If I press "Fetch", I expect it to fetch no matter what. I think this is a bad idea, and the current behaviour is sufficient.
I agree, I consider such a feature as confusing. We should follow the Keep-It-Simple principle here. First, fetch would not work like expected, second you got a cluttered UI and third, who presses "Fetch All" every minute? (you have to be very bored to do so ;) ).
*** Bug 102877 has been marked as a duplicate of this bug. ***
Everything was said in #4.