OpenCloud
/
MatrixSynapse
mirror of https://github.com/matrix-org/synapse
1
0
Fork 0
Code Issues Releases Wiki Activity

Rephrase

pull/6891/head
Brendan Abolivier 2020-02-12 15:39:40 +00:00
parent a0c4769f1a
commit 08e050c3fd
No known key found for this signature in database
GPG Key ID: 1E015C145F1916CD
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/admin_api/purge_history_api.rst
View File

@ -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 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. 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 Note that Synapse requires at least one message in each room, so it will never
message sent to it. delete the last message in a room.
The API is: The API is:

6
docs/message_retention_policies.md
View File

@ -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, process and store that event until it's picked up by the next purge job,
though it will always hide it from clients. though it will always hide it from clients.
With the current implementation of this feature, in order not to break Synapse requires at least one message in each room, so it will never
rooms, Synapse will never delete the last message sent to a room, and delete the last message in a room. It will, however, hide it from
will only hide it from clients. clients.
## Server configuration ## Server configuration