Chats pruning (one-to-one and groups) #640

New Issue

serrq · 2023-03-05T07:26:31Z

serrq commented

2023-03-05 07:26:31 +00:00

In order to keep the backup of an account short and light, but also to have shorter recovery times (think about groups or those very long chats) I ask that it be introduced the possibility of setting a length limit for the individual chats and the groups.

This limit should not have a time limit, but a unitary one.

For example: Always keep the last 100 messages.

This limit is set locally, on the client device, so the server (in the case of groups) will only deliver the client messages that meet its local rule (which is a user-decided value).

In order to keep the backup of an account short and light, but also to have shorter recovery times (think about groups or those very long chats) I ask that it be introduced the possibility of setting a length limit for the individual chats and the groups. This limit should not have a time limit, but a unitary one. For example: Always keep the last 100 messages. This limit is set locally, on the client device, so the server (in the case of groups) will only deliver the client messages that meet its local rule (which is a user-decided value).

sarah commented

2023-03-06 20:23:54 +00:00

This is something we discussed in the very early days of Cwtch, and I believe an early prototype might have even had support for it but it never migrated past alpha.

Ideally I think we would allow both time-based pruning (save messages for 1 day / week / month), and absolute pruning (100 max messages).

There is already a prune messages api in cwtch that checks the save history status. It would not be too much work to have it check additional qualifiers.

Related to: #608

This is something we discussed in the very early days of Cwtch, and I believe an early prototype might have even had support for it but it never migrated past alpha. Ideally I think we would allow both time-based pruning (save messages for 1 day / week / month), and absolute pruning (100 max messages). There is already a prune messages api in cwtch that checks the save history status. It would not be too much work to have it check additional qualifiers. Related to: https://git.openprivacy.ca/cwtch.im/cwtch-ui/issues/608

sarah added the

enhancement

help wanted

component/cwtch

labels 2023-03-06 20:24:12 +00:00

decentral1se referenced this issue from cwtch.im/server

2023-06-11 21:27:29 +00:00

Disappearing Messages Supported? #36

sarah added the

stable-blocker

label 2023-08-14 16:54:07 +00:00

sarah added this to the Stable Blockers project 2023-08-14 17:17:22 +00:00

sarah referenced this issue

2023-09-25 19:56:03 +00:00

Allow deletion of message history (for groups in particular) #608

sarah modified the project from Stable Blockers to Post-Stable

2023-09-25 19:56:53 +00:00

sarah commented

2023-09-25 19:58:08 +00:00

After consideration, given the work we are planning with hybrid groups after stable, and given the legacy state of groups, this work is being rescheduled until after stable.

domelike commented

2024-02-02 23:22:56 +00:00

Is the timeline on this for after the (very exciting) work on groups? The absence of time-based pruning is the only hesitation I currently have for using Cwtch in some use cases, and I imagine some other users might also really value this feature.