Only pull user configs that have been edited since last check

[rossjrw]

[rossjrw]

Huge problem with the proposed method of fetching only those configs that have been edited since the last check: deleted configs will not be captured. If this is the only check I do, a deleted config will be presumed to exist and will not be distinguishable from one that has not been edited.

The only way to get around this is to construct a query that I know for sure contains a given config, and then verify that it doesn't.

I think the only way I can do this, other than listpagesing all configs as I'm doing currently, is to query each config page individually and check that it exists. That can be done during the notification, after getting the list of users to notify in the current run but before sending the notification itself, as that minimises the number of users.

I don't know if that is more efficient than listing all pages. The worst case for sending notifications seems to be about 14, and the fill config list can fit into 4 listpages pages, almost 5. Is 14 standard page hits less load than 5 full listpages requests?