On Mon, Feb 17, 2014 at 4:12 PM, Aristotle Pagaltzis <pagaltzis@gmx.de> wrote:

the database schema does not seem to contain such information, nor does
the OPML file, and I can’t find it in GConf either. So I went hunting
for it in the source code, but over an hour of grepping hasn’t revealed
anywhere that updateState might be getting stored.

Does it persist this information somehow that I cannot find, or not, as
it’s starting to seem?

If not, then how does Liferea behave if the “Update all subscriptions at
startup” pref is off?

(What I want is to be able to forcibly scatter the scheduled updates of
my feeds evenly across my default update interval of ~6 hours – because
I have ~700 of them. And I want to be able to do this any time Liferea
has been down for a few hours.)

Hi Aristotle,

The last update time is not persisted in the database. It is reset to the
current timestamp on startup. So if "Update all subscription at start" is off
and a subscription has an update interval of 1 day it will last one day until
it is updated.

I mostly see three main use cases:

1.) User wants to mass-update on startup and then read through everything

2.) User manually updates when pulling up Liferea to control the act of updating

3.) Always on scenario: Liferea is never/rarely shut down

Given the current implementation randomization is not possible via configuration.

For your use case may I ask why you want to randomize the updates?
Is it to avoid too many Liferea-internal connections or to do to much HTTP
traffic in general?

As a solution the code for resetting the update counter on startup can be changed
to a random number between e.g. 5min to the default or feed specific update interval.