Configurable message expiration

[kruthoff]

For a long-running chat, I would prefer to set message expiration to 6 Months or to 1 Year, or to define my own retention time, i.e. 180 Days.

It would be cool to expire existing talk messages with this new feature of NC 25. The feature is activated just for new messages, as far as I understand.

Thanks for your support!

[HuguesDug]

Hello,

While we would implement more customizing in the "expiring messages", could be nice to give the option to user to get all messages removed either when time limit is reached or ONLY for the ones that have been read by all participants.

So far, I do this while having a event running on the SQL server, changing the date of the expire_date field in table oc_comments. It checks if message id is lower thant the last read message Id for each user in the room, and, if so, I deduct 180 days from the current expire_date. At next nextcloud cron job, the messages are then removed gently. But in everycase, when time is reached, read or not, it goes away, what can be annoying.

Works fine, except on IOS-talk, that has message caching implemented. So the expire_date is kept to original value on the local system, and read message goes away on these devices only if expiring limit is reached, being read of not. That is annoying from privacy standpoint but also, some users could miss some portions of the conversation.

[marcotrevisan]

I would like to add to @kruthoff's requirement: it would be nice to also have the option to delete only the attachments older than "X", leaving the messages (I'm borrowing this from a popular chat server we are using which has this option too and it's very useful).

[t0maz]

I miss this feature too.

Additionally it would be great if admin can set default messages expiration time and have ability to enforce max expiration time (users would have ability to set lower one but not higher value).