Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Commit

Permalink
Rephrase
Browse files Browse the repository at this point in the history
  • Loading branch information
babolivier committed Feb 12, 2020
1 parent a0c4769 commit 08e050c
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions docs/admin_api/purge_history_api.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,8 @@ Depending on the amount of history being purged a call to the API may take
several minutes or longer. During this period users will not be able to
paginate further back in the room from the point being purged from.

Note that, in order to not break the room, this API won't delete the last
message sent to it.
Note that Synapse requires at least one message in each room, so it will never
delete the last message in a room.

The API is:

Expand Down
6 changes: 3 additions & 3 deletions docs/message_retention_policies.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 08e050c

Please sign in to comment.