summary refs log tree commit diff
path: root/docs/message_retention_policies.md
diff options
context:
space:
mode:
authorBrendan Abolivier <babolivier@matrix.org>2020-02-11 17:37:09 +0000
committerBrendan Abolivier <babolivier@matrix.org>2020-02-11 17:37:09 +0000
commita443d2a25dc3cd99519c6b9a3a326545a0b2f933 (patch)
tree0d76b6c35b33cce96403f527050c835358a8c54a /docs/message_retention_policies.md
parentMerge branch 'release-v1.10.0' into develop (diff)
downloadsynapse-a443d2a25dc3cd99519c6b9a3a326545a0b2f933.tar.xz
Spell out that Synapse never purges the last event sent in a room
Diffstat (limited to 'docs/message_retention_policies.md')
-rw-r--r--docs/message_retention_policies.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/message_retention_policies.md b/docs/message_retention_policies.md
index 4300809dfe..f2e2794252 100644
--- a/docs/message_retention_policies.md
+++ b/docs/message_retention_policies.md
@@ -42,6 +42,10 @@ purged according to its room's policy, then the receiving server will
 process and store that event until it's picked up by the next purge job,
 though it will always hide it from clients.
 
+With the current implementation of this feature, in order not to break
+rooms, Synapse will never delete the last message sent to a room, and
+will only hide it from clients.
+
 
 ## Server configuration