-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
make clearer that "database encryption" is highly experimental and will slow down devices and notifications #1989
Comments
in general, iirc, sqlcipher uses key derivation, which is slow by design this is also the reason that we keep database and app open in background as long as we can nb: for me even unencrypted desktop takes a handful of seconds to start with a large database (another annecdotical datapoint :) - so 5s on a maybe older phone may be just fine so, you'd need to provide more information and measurements, however, as the whole thing is experimental, and questionable on iOS at all, not sure if i would throw much time on that currently but i agree, for notifications that may be really bad, if you have a small timeslot only. maybe we should end that experiment completely and reconsider when notofications are improved |
we can not do that because of #1979, maybe if we change where the db is saved and change how the share-extension works? maybe then apple would allow us to hold the locks in the background?
On desktop:
That's why other programs like keepass offer a way to test how many derivations you can do in one second and apply that value. |
if we fix crashes: what prevents us from running the possible 30 seconds in the background? |
sure, sure, sure. i wanted to point out that 5-6 seconds may be normal for larger databases and slower devices anyways, as discussed one-to-one, sqlcipher discussions, as being an experimental side-thing, should be removed from notification discussions, it is unclear how useful sqlcipher is on iOS at all. but we can make things clearer in the UI that the feature is not recommended at all and will slow down things (eg. on anroid, we speak of "Highly experimental - use at your own risk") i will do a pr for that |
FTR: I seem to not have this (6 second) problem when there is no debugger attached, but I need to look at this aspect for a few more days using the current version. |
This delays appstart and thus is annoying at least.
Also could be another contributing factor to our notification problems.
The text was updated successfully, but these errors were encountered: