Don't issue so many requests

Right now, we always request all the data.

Loading existing archive
Get user info
Get new statuses
..................
Added a total of 320 new items
Get new favourites
..................o
Added a total of 261 new items
Get new notifications and look for mentions
..................................................................................................................X
Added a total of 326 new items

This shouldn't be necessary. We should take advantage of pagination and only fetch newer items by default. We used to have code like this! This is problematic if the first request refers to an id that got deleted in the mean time. Thus, we should maybe start with id n-20 to make sure we catch the problem of having deleted the last few messages. Only if this fails should we fetch all of the items like we do now.

Adding an option to override this is optional. Why should we have a database where ids somewhere in the middle exist online not offline?


I tried once again to get this working, but I just can't. So I'm closing this, again. Very frustrating.

Tags: Closed

Reopen issue

Comments


This wiki uses a variant of Markdown.

To save this page you must answer this question:

Please write "new issue" into the field below.