Dino: [FR] Option for limited history lifetime

[NicoHood]

It would be cool to have a feature that limits the lifetime of your history. E.g. 7 days or so. Also I am wondering if the messages are encrypted on my disk and how the key is saved.

[mar-v-in]

Dino does not encrypt messages stored on your disk. If you want to have your messages encrypted, you should use disk encryption (luks) or directory encryption (ecryptfs). The history, account passwords and your omemo keys are stored in the directory $HOME/.local/share/dino.

If you want to encrypt messages to prohibit other apps on your device to access them (e.g. your browser) you can use tools like firejail to cleanly separate possible vulnerable apps. This seems also to be partly a reason for your request #66, so you might want to consider this anyway.

The request for history lifetime limitation is still valid though ;)

[NicoHood]

Even though alternatives like firejail are available I think it is still a good idea to keep messages secure. I already have full disk encryption, but encrypted messages would still be a feature I wish. And especially a limited history could solve this partly (for now).

66 is also a general issue. You cannot and dont want to put everything inside a firejail sandbox. Also just because other might want to login on your pc. And password remembering should not be enabled by default.

[mejo-]

I agree that an option for limited history lifetime - and even more important - an option to completely turn off local history for specific contacts/channel is a crucial option for users who care about privacy.

[martin21]

Being able to delete history is an important privacy feature. A chat buddy requested to me to delete chat history from time to time, yet, currently, I can't. I am trying to figure out the SQLite database. I find the messages with select * from message;, however I see no key that is unique for the chat partner. I bet I need to build a relation with another table.

Can you provide any hint how to manually delete the chat history of one chat with SQLite3 but not the chat itself – except maybe the last few days? I understand you cannot implement everything at once, however I just got that request of the chat buddy again and for me it is a completely reasonable request.

[martin21]

Found it, appears to work like SELECT * FROM message WHERE counterpart_id = SOMEID;