`matrix_synapse.egg-info/`

Mentioned at https://matrix.to/#/!vcyiEtMVHIhWXcJAfl:sw1v.org/$aKy_IjrKwb70aTVZWeW_6zt0k7OIZ1YkyZpkP9uiRaM?via=matrix.org&via=element.io&via=beeper.com and many other places.

Be able to correlate timeouts in reverse-proxy layer in front of Synapse (pull request ID from header) (#13801)

Fix https://github.com/matrix-org/synapse/issues/13685

New config:

```diff
  listeners:
    - port: 8008
      tls: false
      type: http
      x_forwarded: true
+     request_id_header: "cf-ray"
      bind_addresses: ['::1', '127.0.0.1', '0.0.0.0']
```

Co-authored-by: reivilibre <olivier@librepush.net>

* Notify that SQLite min version will be bumped
* Mention in upgrade notes

Co-authored-by: reivilibre <oliverw@matrix.org>

This adds two new admin APIs that allow us to fetch messages from a room within a particular time.

Removes the ability to configure legacy direct TCP replication. Workers now require Redis to run.

Summarized from @richvdh's reply at https://github.com/matrix-org/synapse/pull/13589#discussion_r961116999

It was really easy to miss the `enable_metrics: True` step with the previous language.

* Add monthly active users documentation

* changelog

* Tidy up notes

* more tidyup

* Rewrite #1

* link back to mau docs

* fix links

* s/appservice|AS/application service

* further review

* a newline

* Remove bit about shadow banned users.

I think talking about them is confusing, and the current text doesn't imply they get any special treatment.

* Update docs/usage/administration/monthly_active_users.md

Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>

* Update docs/usage/administration/monthly_active_users.md

Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>

Co-authored-by: Brendan Abolivier <babolivier@matrix.org>
Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>

Borrows some text from https://github.com/matrix-org/synapse/pull/13647
for the changelog.

This has been the same as a generic_worker since #6964, so let's get rid of it.

Fixes #3717

It can be authenticated with the worker_replication_secret setting,
but is always unencrypted.

Update a bunch of the documentation for user registration, add some cross
links, etc.

If things like the signing key file are missing, let's just try to generate
them on startup.

Again, this is useful for k8s-like deployments where we just want to generate
keys on the first run.

A new `registration_shared_secret_path` option. This is kinda handy for k8s deployments and things.

Co-authored-by: Sean Quah <8349537+squahtx@users.noreply.github.com>

Linking the help article may prevent confusion regarding the creation of the necessary rule using auth0.

Cross-ref #13525

Implement MSC3852: Expose `last_seen_user_agent` to users for their own devices; also expose to Admin API (#13549)

Closes #13415.

Signed-off-by: Ayush Anand <iamayushanand@gmail.com>

Signed-off-by: Dirk Klimpel <dirk@klimpel.org>

Signed-off-by: James Barton <james@neodon.com>

Add note to `redaction_retention_period` documentation mentioning that event purging runs at most every 5m (#13492)