Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Add note to 'federation_domain_whitelist' option #16416

Merged
merged 2 commits into from
Oct 3, 2023
Merged

Add note to 'federation_domain_whitelist' option #16416

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7bde9e0
Add note to 'federation_domain_whitelist' option
erikjohnston Oct 2, 2023
a842e5d
Newsfile
erikjohnston Oct 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/16416.doc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Add note to `federation_domain_whitelist` config option to clarify its usage.
5 changes: 5 additions & 0 deletions docs/usage/configuration/config_documentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1190,6 +1190,11 @@ 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:
```yaml
federation_domain_whitelist:
Expand Down