|
What bugs me is that this should be an easily solved problem. It suggests that the Kobo software is not simply looking to see if the current page index is not behind the 'synced' index, or this would never happen. I suspect there's probably a timestamp it's checking against instead, e.g. book was last opened at 2025/10/04 11:00 AM on this device and last datetime is 2025/10/04 12:02 AM on the cloud side, ergo current book's progress should become new milestone.
But how hard would it be to just validate first that I actually read a page in my book after opening it before updating the timestamp? Opening the book, realizing it's chapters behind, and then closing it so that I can try to sync should not count towards resetting the timestamp...
|