1736 commits

Author	SHA1	Message	Date
Travis Ralston	09649fce2a	Merge branch 'develop' into travis/auth-always-on	2024-11-18 09:19:18 -07:00
Richard van der Hoff	d72843056b	Add some documentation about backing up Synapse (#17931) ... Fixes: https://github.com/element-hq/element-meta/issues/2155 Fixes: https://github.com/element-hq/synapse/issues/2046	2024-11-18 14:05:49 +00:00
Poruri Sai Rahul	c812a79422	Removal: Remove support for experimental msc3886 (#17638)	2024-11-13 14:10:20 +00:00
reivilibre	20fc9fcc33	Clarify the semantics of the enable_authenticated_media configuration option. (#17913) ... Signed-off-by: Olivier 'reivilibre <oliverw@matrix.org>	2024-11-11 10:44:47 +00:00
Travis Ralston	0f8d3a66a6	Merge branch 'develop' into travis/auth-always-on	2024-11-07 09:57:41 -07:00
Devon Hudson	eda735e4bb	Remove support for python 3.8 (#17908) ... ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2024-11-06 19:36:01 +00:00
Erik Johnston	361bdafb87	Add experimental support for MSC4222 (#17888) ... Basically, if the client sets a special query param on `/sync` v2 instead of responding with `state` at the *start* of the timeline, we instead respond with `state_after` at the *end* of the timeline. We do this by using the `current_state_delta_stream` table, which is actually reliable, rather than messing around with "state at" points on the timeline. c.f. MSC4222	2024-11-05 14:45:57 +00:00
Travis Ralston	0f65bcc26b	changelog	2024-10-30 10:56:24 -06:00
Travis Ralston	4a47ad6638	Enable authenticated media by default	2024-10-30 09:59:28 -06:00
Shay	58deef5eba	Add admin handler to list of handlers used for background tasks (#17847) ... Fixes #17823 While we're at it, makes a change where the redactions are sent as the admin if the user is not a member of the server (otherwise these fail with a "User must be our own" message).	2024-10-29 13:50:13 -05:00
Andrew Morgan	5d47138b46	Fix typo in target_cache_memory_usage docs (#17825)	2024-10-14 13:34:55 +01:00
Andrew Morgan	451a9dc7b9	Clarify when 3PID invite module callbacks are called (#17627) ... Co-authored-by: Eric Eastwood <eric.eastwood@beta.gouv.fr>	2024-10-14 11:31:49 +01:00
Nathan	05576f0b4b	Added display_name_claim in jwt_config which sets the user's display name upon registration (#17708)	2024-10-09 12:21:08 +00:00
Andrew Ferrazzutti	bdcc9fa388	Fix incorrectly documented config path argument (#17802)	2024-10-08 15:05:36 +01:00
V02460	e8e0f0fad7	Add config option redis.password_path (#17717) ... Adds the option to load the Redis password from a file, instead of giving it in the config directly. The code is similar to how it’s done for `registration_shared_secret_path`. I changed the example in the documentation to represent the best practice regarding the handling of secrets. Reading secrets from files has the security advantage of separating the secrets from the config. It also simplifies secrets management in Kubernetes.	2024-10-07 09:46:51 +01:00
Henrique	beb7a951f4	docs: add note about PYTHONMALLOC for accurate jemalloc memory tracking (#17709) ... Added a note in the documentation suggesting that users may set `PYTHONMALLOC=malloc` when using `jemalloc`. This allows jemalloc to track memory usage more accurately by bypassing Python's internal small-object allocator (`pymalloc`), helping to ensure that `cache_autotuning` functions as expected. This doc change aims to provide more clarity for users configuring jemalloc with Synapse. Based on: 4ac783549c/synapse/metrics/jemalloc.py (L198-L201)	2024-10-07 08:37:39 +00:00
Dirk Klimpel	8bbe66a9b9	explain load balancing for federation_sender_instances (#17776) ... Adding information on how the load is distributed for `federation_sender_instances`. Thx to @devonh for the information. causal source: c2e5e9e67c/synapse/config/_base.py (L946-L989) ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [x] Pull request is based on the develop branch * [x] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [x] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Devon Hudson <devon.dmytro@gmail.com>	2024-10-03 22:01:33 +00:00
Erik Johnston	f144b4c7e9	Remove spurious TODO in debian install step (#17749) ... This was a note added in the PR to move to AGPL, which we failed to remove before landing. (The context for this was that we needed to decide if we were going to change which debian repository we published too, but decided not to in the end)	2024-09-26 13:18:28 +01:00
Andrew Ferrazzutti	5173741c71	Support MSC4140: Delayed events (Futures) (#17326)	2024-09-23 13:33:48 +01:00
Shay	51dd4df0a3	Add an Admin API endpoint to redact all a user's events (#17506)	2024-09-18 10:08:01 +00:00
V02460	e06e3c4004	Add config option turn_shared_secret_path (#17690) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2024-09-10 17:27:46 +00:00
Quentin Gliech	cdd5979129	Replace isort and black with ruff (#17620) ... Ruff now has decent parity with black and isort, so this is going to just save us a bunch of time	2024-08-30 10:07:46 +02:00
meise	a8f29c9913	docs: fix typo in saml2_config example (#17594)	2024-08-29 10:39:16 +00:00
Dirk Klimpel	9eed8cd878	fix listener docs - admin api only on main process (#17590)	2024-08-29 10:33:14 +00:00
Eric Eastwood	11db575218	Sliding Sync: Use stream_ordering based timeline pagination for incremental sync (#17510) ... Use `stream_ordering` based `timeline` pagination for incremental `/sync` in Sliding Sync. Previously, we were always using a `topological_ordering` but we should only be using that for historical scenarios (initial `/sync`, newly joined, or haven't sent the room down the connection before). This is slightly different than what the [spec suggests](https://spec.matrix.org/v1.10/client-server-api/#syncing) > Events are ordered in this API according to the arrival time of the event on the homeserver. This can conflict with other APIs which order events based on their partial ordering in the event graph. This can result in duplicate events being received (once per distinct API called). Clients SHOULD de-duplicate events based on the event ID when this happens. But we've had a [discussion below in this PR](https://github.com/element-hq/synapse/pull/17510#discussion_r1699105569) and this matches what Sync v2 already does and seems like it makes sense. Created a spec issue https://github.com/matrix-org/matrix-spec/issues/1917 to clarify this. Related issues: - https://github.com/matrix-org/matrix-spec/issues/1917 - https://github.com/matrix-org/matrix-spec/issues/852 - https://github.com/matrix-org/matrix-spec-proposals/pull/4033	2024-08-07 11:27:50 -05:00
Andrew Morgan	244a255065	Clarify auto_accept_invites.worker_to_run_on config docs (#17515)	2024-08-06 13:26:51 +01:00
YLong Shi	69ac4b6a6e	Update config_documentation - Change example of msisdn in allowed_local_3pids (#17476) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2024-07-25 11:07:44 +00:00
Michael Hollister	a9ee832e48	Fixed presence results not returning offline users on initial sync (#17231) ... This is to address an issue in which `m.presence` results on initial sync are not returning entries of users who are currently offline. The original behaviour was from https://github.com/element-hq/synapse/issues/1535 This change is useful for applications that use the presence system for tracking user profile information/updates (e.g. https://github.com/element-hq/synapse/pull/16992 or for profile status messages). This is gated behind a new configuration option to avoid performance impact for applications that don't need this, as a pragmatic solution for now.	2024-07-23 09:59:24 +00:00
Shay	dc8ddc6472	Prepare for authenticated media freeze (#17433) ... As part of the rollout of [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3916-authentication-for-media.md) this PR adds support for designating authenticated media and ensuring that authenticated media is not served over unauthenticated endpoints.	2024-07-22 10:33:17 +01:00
Ben Banfield-Zanin	6a01af59e1	Improve default_power_level_content_override documentation (#17451) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2024-07-18 13:32:32 +01:00
villepeh	342f0c35b7	Add Red Hat Enterprise Linux and Rocky Linux installation instructions (#17423) ... Added RHEL/Rocky install instructions (PyPI). Instructions cover versions 8 and 9 which are the only supported ones - except for RHEL7 which is now on extended life cycle support phase. Large part of the guide is for installing Python 3.11 or 3.12. RHEL8 ships with Python 3.6 and RHEL9 ships with 3.9. Newer Python versions can be installed easily as they don't interfere with OS software that still relies on the default Python version. I was first planning to add prerequisites part to the prerequisites section and then install instructions on the top of the page but that section is for pre-built packages so it just didn't sound right. So I just dumped everything to the PyPI section of the page. But suggestions to change are welcome. I also didn't combine these with Fedora section. I haven't tested those packages on RHEL and Fedora ships with Python 3.12 out-of-box.	2024-07-11 14:02:19 +01:00
Will Lewis	3232bc2982	Upload new logo with white bg and update readme to use it (#17387)	2024-07-10 14:59:24 +01:00
Andrew Morgan	62d8b0361b	Note the new federated media worker endpoints in the worker docs & upgrade notes (#17421)	2024-07-09 16:41:51 +01:00
Erik Johnston	8e9e6f1a0a	Allow enabling sliding sync per-user (#17393) ... Based on #17392	2024-07-05 13:04:27 +01:00
Erik Johnston	57538eb4d9	Finish up work to allow per-user feature flags (#17392) ... Follows on from @H-Shay's great work at https://github.com/matrix-org/synapse/pull/15344 and MSC4026. Also enables its use for MSC3881, mainly as an easy but concrete example of how to use it.	2024-07-05 13:02:35 +01:00
Eric Eastwood	a9d2e40ea4	Changelog entries only get merged if they have the same content and extension (#17399) ... Changelog entries only get merged if they have the same content and extension See https://github.com/element-hq/synapse/pull/17301#discussion_r1665387218	2024-07-04 17:21:25 +01:00
Shay	8f890447b0	Support MSC3916 by adding _matrix/client/v1/media/download endpoint (#17365)	2024-07-02 14:07:04 +01:00
davidegirardi	b11f5c984b	Clarify url_preview_url_blacklist is a usability feature (#17356)	2024-06-28 14:39:54 +01:00
Denis Kasak	9cf0ef9c70	Fix outdated Security Disclosure Policy references (#17341)	2024-06-25 15:58:30 +01:00
douglaz	f79dbd0f61	Fix refreshable_access_token_lifetime typo (#17357) ... Simple typo in the docs	2024-06-25 12:07:13 +01:00
devonh	805e6c9a8f	Correct error in user_directory docs (#17348) ... ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> Co-authored-by: reivilibre <oliverw@matrix.org>	2024-06-24 17:18:58 +00:00
devonh	3c61ddbbc9	Add default values for rc_invites per_issuer to docs (#17347) ... A simple change to update the docs where default values were missing. ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Kim Brose <2803622+HarHarLinks@users.noreply.github.com> Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2024-06-24 17:16:09 +00:00
Alexander Fechler	9104a9f0d0	Filter added to Admin-API GET /rooms (#17276)	2024-06-19 11:45:48 +01:00
Dirk Klimpel	1c7d85fdfe	fix missing quotes for exclude_rooms_from_sync (#17308) ... We tried to configure rooms `exclude_rooms_from_sync`. If we do not quote we get an error. The example should be valid.	2024-06-18 10:37:02 +01:00
Quentin Gliech	e88332b5f4	Merge branch 'release-v1.109' into develop	2024-06-17 15:51:16 +02:00
Erik Johnston	a3cb244755	Automatically apply SQL for inconsistent sequence (#17305) ... Rather than forcing the server operator to apply the SQL manually. This should be safe, as there should be only one writer for these sequences.	2024-06-14 16:40:29 +01:00
Shay	fcbc79bb87	Ratelimiting of remote media downloads (#17256)	2024-06-05 13:43:36 +01:00
Erik Johnston	967b6948b0	Change allow_unsafe_locale to also apply on new databases (#17238) ... We relax this as there are use cases where this is safe, though it is still highly recommended that people avoid using it.	2024-05-29 12:04:13 +01:00
Yadd	a547b49773	Update Lemonldap-NG OIDC config (#17204) ... Update OIDC documentation: by default Matrix doesn't query userinfo endpoint, then claims should be put on id_token.	2024-05-22 12:29:31 +00:00
devonh	6a9a641fb8	Bring auto-accept invite logic into Synapse (#17147) ... This PR ports the logic from the [synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite) module into synapse. I went with the naive approach of injecting the "module" next to where third party modules are currently loaded. If there is a better/preferred way to handle this, I'm all ears. It wasn't obvious to me if there was a better location to add this logic that would cleanly apply to all incoming invite events. Relies on https://github.com/element-hq/synapse/pull/17166 to fix linter errors.	2024-05-21 20:09:17 +00:00