From 747fa72df3d005f79ab56c39ffe68be6bc0d2a6e Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Tue, 3 Oct 2023 08:56:29 +0000 Subject: deploy: 1e67191a79a06fb4031b17c24b4621c066345182 --- develop/usage/configuration/config_documentation.html | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'develop/usage/configuration/config_documentation.html') diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html index 9bd005eae5..1753dca599 100644 --- a/develop/usage/configuration/config_documentation.html +++ b/develop/usage/configuration/config_documentation.html @@ -1163,6 +1163,10 @@ N.B. we recommend also firewalling your federation listener to limit inbound federation traffic as early as possible, rather than relying purely on this application-layer restriction. If not specified, the default is to whitelist everything.

+

Note: this does not stop a server from joining rooms that servers not on the +whitelist are in. As such, this option is really only useful to establish a +"private federation", where a group of servers all whitelist each other and have +the same whitelist.

Example configuration:

federation_domain_whitelist:
   - lon.example.com
-- 
cgit 1.5.1