▲ | Silhouette 6 days ago | ||||||||||||||||
Note that in all cases, Signal could/should still fully encrypt this data before pushing it to the provider; the backup wouldn't be expected to be "legible" to the user. That seems like an unhelpful limitation for a lot of people. For me - and as far as I know literally everyone I communicate with using Signal - the reason to use it is the E2EE for the messages. Once we have the messages or media on our own devices we're fine with having control over them ourselves. By all means also provide an option to create a secured archive for those who want it. But as long as the data can only be read using a specific app on a specific device then whatever you're creating isn't really a backup for a lot of practical purposes. | |||||||||||||||||
▲ | varenc 6 days ago | parent [-] | ||||||||||||||||
Agree with the sentiment, but I can understand why they don't offer this. Rational or not, people will feel less safe if all their messages can just be easily exported to plaintext. A few scenarios where this might matter like the 'evil maid attack' where someone briefly has access to your unlocked phone. But I just use this project to export my signal messages to plaintext: https://github.com/tbvdm/sigtop I have it auto run periodically and it's great. Makes for easy full text searching of my message history. | |||||||||||||||||
|