diff --git a/develop/message_retention_policies.html b/develop/message_retention_policies.html index c4e8fc8b88..d862405ebc 100644 --- a/develop/message_retention_policies.html +++ b/develop/message_retention_policies.html @@ -155,7 +155,8 @@ and allow server and room admins to configure how long messages should be kept in a homeserver's database before being purged from it. Please note that, as this feature isn't part of the Matrix specification yet, this implementation is to be considered as -experimental.

+experimental. There are known bugs which may cause database corruption. +Proceed with caution.

A message retention policy is mainly defined by its max_lifetime parameter, which defines how long a message can be kept around after it was sent to the room. If a room doesn't have a message retention diff --git a/develop/print.html b/develop/print.html index 40cf732869..bc2ae6bfb4 100644 --- a/develop/print.html +++ b/develop/print.html @@ -3836,7 +3836,11 @@ the allowed_lifetime_min and allowed_lifetime_max conf which are older than the room's maximum retention period. Synapse will also filter events received over federation so that events that should have been purged are ignored and not stored again.

-

The message retention policies feature is disabled by default.

+

The message retention policies feature is disabled by default. Please be advised +that enabling this feature carries some risk. There are known bugs with the implementation +which can cause database corruption. Setting retention to delete older history +is less risky than deleting newer history but in general caution is advised when enabling this +experimental feature. You can read more about this feature here.

This setting has the following sub-options: