Skip to content
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

Auto Delete old messages after given time #363

Open
adeorato opened this issue May 26, 2022 · 9 comments
Open

Auto Delete old messages after given time #363

adeorato opened this issue May 26, 2022 · 9 comments
Labels
A-Message-Editing A-Timeline O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement

Comments

@adeorato
Copy link

Your use case

What would you like to do?

I want to have old messages automatically deleted from the local file system. E.g. after x days or only keep newest 50 (e.g.) messages.

Why would you like to do it?

There are three reasons:

  1. Disk storage -> What has been deleted does not need storage space.
  2. I can't exclude that others get physical access to the PC. What has been deleted cannot be read by the attacker.

How would you like to achieve it?

The other participants still have the message. I am aware of that. Here it is only about the own physical device.
If I delete a mail, I also don't expect that the other person doesn't have it anymore.

Here I wish as an implementation that there is a timer per "chat/room" that deletes old message locally after timer expires and also does not re-download from server (or sends a delete to server, whatever is easier to implement).
Alternatively, that it displays a configurable maximum number of messages and deletes the older ones locally. Expressed as SQL:
"select ... order by id desc fetch first ? rows only"
and everything not found by the query will be deleted

Have you considered any alternatives?

Delete messages manually.
However, since it is not possible to delete multiple messages at once, this is not an acceptable alternative.

At the moment, I use other clients for more critical stuff, as Elements doesn't meet my security requirement in that regard.

Additional context

No response

@t3chguy
Copy link
Member

t3chguy commented May 26, 2022

Duplicate of #729

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2022
@adeorato
Copy link
Author

@t3chguy no this is not a duplicate. #729 is about server side. This bug is about client side.
I already learned that server side won't be done (federal design leads to no new features) so I opened a FR for the client.

So kindly reopen the FR.

@ShadowJonathan
Copy link

@adeorato you can achieve the same effect (clearing messages) by going to All Settings -> Help & About -> Clear Cache and Reload, this will fetch all required information from the server and drop all local information, including all messages. E2EE data will not be dropped.

@t3chguy
Copy link
Member

t3chguy commented May 26, 2022

Element Web doesn't store history, only a cached window of recent events which can be cleared via the above instructions by @ShadowJonathan.
Element Desktop has an additional encrypted search index to power message search which you can disable.

image

I already learned that server side won't be done

Server side has been done though?

matrix-org/synapse#6358

@adeorato
Copy link
Author

@ShadowJonathan and @t3chguy I tried your suggestions (clear cache and deactivate message search).
I cannot see any difference. All one-to-one chats are still there (with all messages) and no message seems to be missing?

@t3chguy
Copy link
Member

t3chguy commented May 26, 2022

Because they're re-fetched from the server, there's no way to exclude them from /sync

@adeorato
Copy link
Author

And this is what this feature request is about: "also does not re-download from server"

@t3chguy t3chguy reopened this May 26, 2022
@t3chguy t3chguy transferred this issue from element-hq/element-web May 26, 2022
@kittykat kittykat added S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-Timeline O-Occasional Affects or can be seen by some users regularly or most users rarely A-Message-Editing S-Minor Impairs non-critical functionality or suitable workarounds exist and removed S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels May 26, 2022
@ShadowJonathan
Copy link

ShadowJonathan commented May 26, 2022

So you're essentially requesting something like WhatsApp/Telegram's "Delete for me" feature?

@adeorato
Copy link
Author

So you're essentially requesting something like WhatsApp/Telegram's "Delete for me" feature?

Short answer: Essentially yes.

Long answer:
My use case is: If someone gets physically access to my computer he should not be able to restore old messages. I would prefer an automated solution for this (like delete after X days).
If it is deleted on the other communication partner side also, I am fine with it, but this is not a hard requirement. So if the mentioned issue #729 is implemented, I could use this feature instead of this. I opened this feature request, cause 3800 exists since 2017 and I did not believe it will be implemented in a reasonable time.

I don't know if this is important, but I care only about 2 person chats. As far as I understand, this is technically also a room.

So the following list would fulfil my requirement:

  • Delete messages after X days on client (and make sure, no new download is possible). This is what this FR is about. Possible solutions:
    -- Delete remote
    -- Change E2E Keys and delete old keys
    -- any other method someone with physical access to the filesystem cannot bypass
  • Allow multi select for message delete (mark all, press delete like in mail programs). Then I could do this daily by hand
  • Delete messages after X days on server (like Configurable history retention limits for rooms #729) suggests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Message-Editing A-Timeline O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement
Projects
None yet
Development

No branches or pull requests

4 participants