summary refs log tree commit diff
path: root/synapse/config/federation.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* An federation whitelist query endpoint extension (#16848)Erik Johnston2024-05-131-0/+4
| | | | | | | | | | This is to allow clients to query the configured federation whitelist. Disabled by default. --------- Co-authored-by: Devon Hudson <devonhudson@librem.one> Co-authored-by: devonh <devon.dmytro@gmail.com> Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
* Correctly mention previous copyright (#16820)Erik Johnston2024-01-231-0/+1
| | | | | During the migration the automated script to update the copyright headers accidentally got rid of some of the existing copyright lines. Reinstate them.
* Update license headersPatrick Cloke2023-11-211-10/+16
|
* Allow config of the backoff algorithm for the federation client. (#15754)Mathieu Velten2023-08-031-0/+18
| | | | | | | | | | | Adds three new configuration variables: * destination_min_retry_interval is identical to before (10mn). * destination_retry_multiplier is now 2 instead of 5, the maximum value will be reached slower. * destination_max_retry_interval is one day instead of (essentially) infinity. Capping this will cause destinations to continue to be retried sometimes instead of being lost forever. The previous value was 2 ^ 62 milliseconds.
* Allow for the configuration of max request retries and min/max retry delays ↵Mathieu Velten2023-06-211-0/+16
| | | | in the matrix federation client (#15783)
* Revert "Allow for the configuration of max request retries and min/max retry ↵Mathieu Velten2023-06-141-10/+0
| | | | | | delays in the matrix federation client (#12504)" This reverts commit d84e66144dc12dacf71c987a2ba802dd59c0b68e.
* Allow for the configuration of max request retries and min/max retry delays ↵Shay2023-06-091-0/+10
| | | | | | | in the matrix federation client (#12504) Co-authored-by: Mathieu Velten <mathieuv@matrix.org> Co-authored-by: Erik Johnston <erik@matrix.org>
* Remove code generating comments in configuration file (#12941)Shay2022-06-141-39/+0
|
* Disable device name lookup over federation by default (#12616)Andrew Morgan2022-05-041-5/+5
|
* Add missing type hints to config classes. (#12402)Patrick Cloke2022-04-111-3/+4
|
* Use inline type hints in various other places (in `synapse/`) (#10380)Jonathan de Jong2021-07-151-1/+1
|
* Add config option to hide device names over federation (#9945)Aaron Raimist2021-05-111-0/+10
| | | | | Now that cross signing exists there is much less of a need for other people to look at devices and verify them individually. This PR adds a config option to allow you to prevent device display names from being shared with other servers. Signed-off-by: Aaron Raimist <aaron@raim.ist>
* Remove redundant "coding: utf-8" lines (#9786)Jonathan de Jong2021-04-141-1/+0
| | | | | | | Part of #9744 Removes all redundant `# -*- coding: utf-8 -*-` lines from files, as python 3 automatically reads source code as utf-8 now. `Signed-off-by: Jonathan de Jong <jonathan@automatia.nl>`
* Add configs to make profile data more private (#9203)AndrewFerr2021-02-191-0/+10
| | | | | | | Add off-by-default configuration settings to: - disable putting an invitee's profile info in invite events - disable profile lookup via federation Signed-off-by: Andrew Ferrazzutti <fair@miscworks.net>
* Fix the sample config location for the ip_range_whitelist setting. (#8954)Patrick Cloke2020-12-161-12/+0
| | | | Move it from the federation section to the server section to match ip_range_blacklist.
* Default to blacklisting reserved IP ranges and add a whitelist. (#8870)Patrick Cloke2020-12-091-49/+10
| | | | This defaults `ip_range_blacklist` to reserved IP ranges and also adds an `ip_range_whitelist` setting to override it.
* Apply an IP range blacklist to push and key revocation requests. (#8821)Patrick Cloke2020-12-021-15/+25
| | | | | | | | | | | | Replaces the `federation_ip_range_blacklist` configuration setting with an `ip_range_blacklist` setting with wider scope. It now applies to: * Federation * Identity servers * Push notifications * Checking key validitity for third-party invite events The old `federation_ip_range_blacklist` setting is still honored if present, but with reduced scope (it only applies to federation and identity servers).
* Add prometheus metrics to track federation delays (#8430)Richard van der Hoff2020-10-011-1/+26
| | | | | Add a pair of federation metrics to track the delays in sending PDUs to/from particular servers.
* Update worker docs with recent enhancements (#7969)Erik Johnston2020-07-291-11/+1
|
* Add ability to run multiple pusher instances (#7855)Erik Johnston2020-07-161-34/+3
| | | This reuses the same scheme as federation sender sharding
* Add ability to shard the federation sender (#7798)Erik Johnston2020-07-101-0/+129
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-09-21 12:24:22 +0000