This is important to limit our API usage, as we don't have a clear way to know what our cap is or how close we are to it.
It should be straightforward, in the item request loop, break early when a last changed timestamp of an item is older than the latest one from the previous attempt.
This may conflict with #23 as, the only way I know of how to do this at the moment, is to check every time and update the database.
This is important to limit our API usage, as we don't have a clear way to know what our cap is or how close we are to it.
It should be straightforward, in the item request loop, break early when a last changed timestamp of an item is older than the latest one from the previous attempt.
This may conflict with #23 as, the only way I know of how to do this at the moment, is to check every time and update the database.