MSC1763: Proposal for specifying configurable message retention periods #1763
This is an attempt to unblock #440 and #447 and solve the problem of how to specify configurable per-room and per-user message retention. This is particularly driven by Disroot & Hackint disabling their Matrix bridges due to concerns over unlimited message retention, and meanwhile there are also corporate Matrix users on the horizon who require configurable history retention. Hence trying to slay the beast for once and for all...
referenced this pull request
Jan 7, 2019
Yes, we should and we should delete the corresponding keys.
We should either have both options available in clients or only purge. I think keeping the integrity of the DAG in this case is only useful for non-serious use cases like sending a message
I don't think it should be - it should be an agreement between the participants of the room. But there could a server-wide policy of maximum retention to save space, in this case a participant cannot set it higher than the lowest maximum retention limit of the participating servers.
A quarantine isn't a good solution to this. Just give room admins an option to prevent messages with short max_lifetime.