New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement more efficient way of submitting highlights #16
Comments
The side effect of #19 relates here. Upon submitting highlights, we need to persist the Readwise IDs to disc, probably mapped to |
Oh, I dunno why it never occured to me but the sync history can just be stored on the Kobo device given it's effectively a USB 🤦 It also means that if you use October on a new computer, it can pick up where it left off instead of blinding syncing everything from scratch. |
I think this can be pushed to post v1.0.0. It's good enough for an initial release. |
The USB storage feature, to be able to use October on different devices, would be helpful. Now I make sure I only sync it from my desktop, but I would love to sync it also from my laptops. Otherwise, there are usually two types of users: I used to do a), but I found if I keep only a few books on the Kobo, I read more, and finish them faster, as there is more focus to read. |
At the moment, everything is just fired off to Readwise.
This is fine but as your Kobo highlights grow, the upload process will naturally become slower.
I was thinking that you could easily tell if a book hasn't changed (and finished books don't) by simply saving hashes for books and seeing if they've changed. We kind of need to retain what content has actually been submitted (not just number of bookmarks) since highlight positions and text annotations can change after the fact.
If they have changed then we ideally just figure out what items are new so perhaps we just hash each bookmark.
It all falls down if someone either is doing a first upload with a squillion highlights (these should be chunked to avoid rate limiting) and/or they use a new computer with a previous upload DB.
It's really cheap to make database calls but expensive (relatively speaking) to fire JSON across the web.
The text was updated successfully, but these errors were encountered: