Scramble has a rather unique challenge when it comes to user data backups.
For example, consider the user's contacts, which are simply replaced on the server upon update. Right now, if a client bug causes all the contacts to get deleted, the user loses his/her contacts list.
We could save the last X revisions on the server.
Related:
How about client encrypted indices? I suppose in the worst case, indices could be rebuilt by fetching everything from the server. It would be expensive, though.
As a user, I want the ability to export & import all my data to and fro scramble servers.
We could store all (or cache some) data on the client machine. What are the limitations here?
Scramble has a rather unique challenge when it comes to user data backups.
For example, consider the user's contacts, which are simply replaced on the server upon update. Right now, if a client bug causes all the contacts to get deleted, the user loses his/her contacts list.
We could save the last X revisions on the server.
Related: