Closed noeleont closed 11 months ago
I think this closes #18
Adding a new feature flag
--use_since
. This enables storing the last synchronization timestamp in a file (since
) and allows for incremental syncing, efficiently updating only the new highlights since the last sync, ideal for large collections.I'm not entirely sure if reading and writing the
since
file should be done in therun.py
script, @e-alizadeh what do you think?
I like the idea of saving the last synchronization timestamp in a file. This would help the automation repo [Zotero2Readwise-Sync](https://github.com/e-alizadeh/Zotero2Readwise-Sync) too.
I believe including it in the run.py
makes the most sense. Obviously, this should be backward-compatible with retrieving everything as the default case. Then, we can update README about this feature.
I like the idea of saving the last synchronization timestamp in a file. This would help the automation repo [Zotero2Readwise-Sync](https://github.com/e-alizadeh/Zotero2Readwise-Sync) too.
Yes I was thinking about Zotero2Readwise-Sync :)
I believe including it in the
run.py
makes the most sense. Obviously, this should be backward-compatible with retrieving everything as the default case. Then, we can update README about this feature.
The way it's implemented it's backward-compatible.
This would close #40
Adding a new feature flag
--use_since
. This enables storing the last synchronization timestamp in a file (since
) and allows for incremental syncing, efficiently updating only the new highlights since the last sync, ideal for large collections.I'm not entirely sure if reading and writing the
since
file should be done in therun.py
script, @e-alizadeh what do you think?