You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Molly currently removes the option to set one of the presets or a custom time as a cooldown for the app's access lock feature. I kindly request that you reimplemente this feature, so users can set the duration just like in the official client, as per their needs. The current default of Molly is 5 seconds, which may fit some people's threat model and use cases for Molly, but definitely not the average, including mine. The current implementation of this Signal feature actually prevents me from using it, which makes Molly, in general, less secure for me, which is the opposite of what a hardened Signal fork should aim for.
TL;DR: Reimplement the custom cooldown feature from the official app for access lock, because the current implementation actually prevents people from using it.
And for everyone who suggests to use database encryption instead, I do use it, but it's too slow and inconvenient to use that it does not work as an good access lock replacement.
The text was updated successfully, but these errors were encountered:
Guidelines
Feature Description
Molly currently removes the option to set one of the presets or a custom time as a cooldown for the app's access lock feature. I kindly request that you reimplemente this feature, so users can set the duration just like in the official client, as per their needs. The current default of Molly is 5 seconds, which may fit some people's threat model and use cases for Molly, but definitely not the average, including mine. The current implementation of this Signal feature actually prevents me from using it, which makes Molly, in general, less secure for me, which is the opposite of what a hardened Signal fork should aim for.
TL;DR: Reimplement the custom cooldown feature from the official app for access lock, because the current implementation actually prevents people from using it.
And for everyone who suggests to use database encryption instead, I do use it, but it's too slow and inconvenient to use that it does not work as an good access lock replacement.
The text was updated successfully, but these errors were encountered: