-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Feature suggestion: sender-controlled message deletion #997
Comments
It might also be nice if "delete old messages" could be based on time ("younger than 1 week") rather than number ("500 messages per conversation"). |
If this feature would be implemented, it would be done on the client side. So the user itself decides, when the messages will be deleted for sent and received messages. If you want thie feature to be added, edit your issue. Otherwise you can close it or the developer will do this. |
In addition to above:
There's a thread on the mailing list about this subject. You can share your ideas there. |
As noted, these are either duplicates or not the right place to discuss these ideas. @2-4601 : Thanks for your comments and work. Terrific as always, can you please email me: fred@whispersystems.org? |
Signal is great for preventing message interception, but it leaves endpoints vulnerable. Messages are stored forever, and can be read by anyone who takes control of the device, unless the recipient deletes messages manually or enables auto-deletion. (Which defaults to the last 500 messages.)
Other "secure messaging apps" enable the sender to set a message expiry time, after which the messages automatically delete. If a friend's phone gets taken and they don't have a strong passcode, or if someone's reading over their shoulder on public transport, the attacker will only see however many minutes/hours/days of conversation that you set for your messages.
I'd very much like a feature in Signal that lets the sender set a message expiration time. This could either be the "$FOO minutes after the user views the message", or "$BAR hours after the device receives the message".
The text was updated successfully, but these errors were encountered: