diff options
| author | Brendan Abolivier <babolivier@matrix.org> | 2020-02-12 15:39:40 +0000 |
|---|---|---|
| committer | Brendan Abolivier <babolivier@matrix.org> | 2020-02-12 15:39:40 +0000 |
| commit | 08e050c3fddb35cc54f6e0704fa9b54128dddc39 (patch) | |
| tree | 7639e45b69ba6f0cd2481fd9a6df31329d0a3ddc /docs/message_retention_policies.md | |
| parent | Update the changelog file (diff) | |
| download | synapse-08e050c3fddb35cc54f6e0704fa9b54128dddc39.tar.xz | |
Rephrase
Diffstat (limited to 'docs/message_retention_policies.md')
| -rw-r--r-- | docs/message_retention_policies.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/message_retention_policies.md b/docs/message_retention_policies.md index f2e2794252..1dd60bdad9 100644 --- a/docs/message_retention_policies.md +++ b/docs/message_retention_policies.md @@ -42,9 +42,9 @@ 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. +Synapse requires at least one message in each room, so it will never +delete the last message in a room. It will, however, hide it from +clients. ## Server configuration |