Open pmartin opened 7 years ago
The current algo works fine for me (I have a lot more unread entries than I have read entries). But it's not the case for everyone, see for example https://twitter.com/nicosomb/status/814919827844464640 (only 24 unread entries in the app, while there are more, older, unread entries on the server).
Hi Pascal, First of all, thanks for this app. I'm encountering this issue right now. I have a lot of read items and can't get the older ones. I don't know if you're using the last API version or the RSS one but we don't have this issue on the Android app. I guess @nicosomb might confirm this.
Today, the synchronization fetches 200 entries (the most recent ones) from the server -- but that 200 includes both unread and read entries.
For a user who reads almost all entries added to her wallabag instance, the current algorithm means she'll have only a small number of unread entries in the app. For example: 177 read entries and only 23 unread entries.
An idea that could possibly be implemented: try to always have at least 100 unread entries in the app, possibly by doing a second fetch after the first one is finished, if it has not fetched enough unread entries?