From 71e01b4e8eb2af428d3447d8ba79ebad5da9055b Mon Sep 17 00:00:00 2001 From: richvdh Date: Fri, 22 Jul 2022 12:51:04 +0000 Subject: deploy: c7c84b81e3ec3d66f3a57a8d6ba3e58dd4c81ecc --- develop/usage/configuration/config_documentation.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'develop/usage/configuration') diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html index 6b71c309ed..9f96da087b 100644 --- a/develop/usage/configuration/config_documentation.html +++ b/develop/usage/configuration/config_documentation.html @@ -1418,6 +1418,7 @@ limit only, as Synapse presumes ratelimiting by room will be done by the sending sender, meaning that a rc_invite.per_user.burst_count of 5 mandates that a single user cannot receive more than a burst of 5 invites at a time.

In contrast, the rc_invites.per_issuer limit applies to the issuer of the invite, meaning that a rc_invite.per_issuer.burst_count of 5 mandates that single user cannot send more than a burst of 5 invites at a time.

+

Changed in version 1.63: added the per_issuer limit.

Example configuration:

rc_invites:
   per_room:
@@ -1430,7 +1431,6 @@ cannot receive more than a burst of 5 invites at a time.

     per_second: 0.5
     burst_count: 5
-

Changed in version 1.63: added the per_issuer limit.

rc_third_party_invite

This option ratelimits 3PID invites (i.e. invites sent to a third-party ID -- cgit 1.5.1