-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Consider moving state to $XDG_STATE_HOME
as opposed to $XDG_CACHE_HOME
#5
Comments
In how far is it safe vs. not safe to delete |
The scariest scenario is when you delete your data, the If you delete the cache, Neverest will not be able to know if sth has been deleted right side or added left side. For now it comes with safe defaults: it will always take the path that does not delete data. Worst case you just get back emails you previously deleted, or get duplicates (same email in trash and inbox). I believe cache is not crucial. It just helps the sync to take the right decision. Hence my initial choice behind the cache directory. That said, the state directory also makes sense, and may be a safer default. So let's do it! |
@soywod Thanks for elaborating! That is quite scary indeed. Would it make sense to add a "readonly" flag to protect either left or right side from accidental changes or a flag to indicate the "direction" of the sync? In my case I'm only ever interested in syncing from left to right. (Except for the hopefully unlikely case when I need to restore |
You have permissions for that purpose: Lines 82 to 91 in 92fa58d
|
To follow-up from our Matrix chat:
Currently,
neverest
stores state/locks in two places:$XDG_CACHE_HOME/pimalaya
and$XDG_RUNTIME_DIR/pimalaya
.The former is the one I'd like to see changed to
$XDG_STATE_HOME/pimalaya
, asstoring in
$XDG_CACHE_HOME/pimalaya
runs the risk of accidental deletion ofthe state files.
The latter isn't as much of an issue.
We could, maybe in the future, store state in the IMAP/Maildir backends as well.
The text was updated successfully, but these errors were encountered: