Rephrase
This commit is contained in:
parent
a0c4769f1a
commit
08e050c3fd
|
@ -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:
|
||||
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue