From 8f769879223c442512acac852566e309e4efb43d Mon Sep 17 00:00:00 2001 From: anoadragon453 Date: Wed, 18 May 2022 11:22:04 +0000 Subject: deploy: deca250e3f0f18ffc978f17d1f9e440fc8a4af98 --- develop/usage/configuration/config_documentation.html | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'develop/usage') diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html index c553f4c6ba..6327fa5e7b 100644 --- a/develop/usage/configuration/config_documentation.html +++ b/develop/usage/configuration/config_documentation.html @@ -1265,6 +1265,17 @@ Defaults to per_second: 0.003, burst_count: 5.

This option sets ratelimiting how often invites can be sent in a room or to a specific user. per_room defaults to per_second: 0.3, burst_count: 10 and per_user defaults to per_second: 0.003, burst_count: 5.

+

Client requests that invite user(s) when creating a +room +will count against the rc_invites.per_room limit, whereas +client requests to invite a single user to a +room +will count against both the rc_invites.per_user and rc_invites.per_room limits.

+

Federation requests to invite a user will count against the rc_invites.per_user +limit only, as Synapse presumes ratelimiting by room will be done by the sending server.

+

The rc_invites.per_user limit applies to the receiver of the invite, rather than the +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.

Example configuration:

rc_invites:
   per_room:
-- 
cgit 1.5.1