Sync should prioritise new master keys and possibly other objects #828
Labels
enhancement
Feature requests and code enhancements
stale
An issue that hasn't been active for a while...
I assume this affects all clients, but I've only observed it on Linux and Android (haven't installed/tested others)
Operating system
Application
Feature Requests
The main issue I observed is there appears to be no prioritisation on how objects are synced. This increases the likelihood of conflicts and other complications.
Sync master keys first
I noticed a fair number of first time users (myself included) running into confusion setting up E2EE with a fairly large number of notes (e.g. importing evernote).
This can be avoided if the sync action prioritises first synching any new master keys?
Some other issues this would help mitigate:
Sync priority for other objects
Maybe there should be an overall sync priority for various objects in terms of importance and size:
4.a New/Edited Note
4.b then New/Edited Resource for note
Maybe to-do note types before normal notes?
And I guess other principles of cache coherency and reliability might apply well to sync use-cases, but I'm no expert on the subject.
The text was updated successfully, but these errors were encountered: