A future release of synapse will, by default, disable federation for servers using SQLite. Instructions for migrating to Postgres are available here.

A future release will refuse to start if used with an SQLite version before 3.11.Īdministrators are reminded that SQLite should not be used for production instances. Support for SQLite versions before 3.11 is now deprecated. This release changes the default settings so that only local authenticated users can query the server's room directory. The changelog since 1.6.1 follows: Synapse 1.7.0 () Also, check out our Synapse installation guide page. We’ll talk more about this closer to the time, but please expect a change in the coming months and if you are running SQLite, consider this a nudge to get yourself migrated.Īs ever, you can get the new update here or any of the sources mentioned at. Overall we see these changes as something that will improve everyone’s experience of the matrix federation. What’s more, in a future release we will forcibly prevent SQLite-backed servers federating unless the admin explicitly sets a config flag to show that they understand the trade-off they are making. Over the past few months we’ve been working to improve the migration path to Postgres such that finally we feel confident to actively encourage admins to migrate. In truth Sqlite is only really there to demonstrate the service, but for anything other than the most trivial cases it is essential to migrate to Postgres. The downside of using Sqlite is that it offers very poor performance, especially once a server tries to join the federation. This is great in that it gets new admins going quickly without needing to install and configure Postgres. Currently Synapse runs Sqlite by default.

We also have early support for ephemeral messages, as well as the ability to specify a reason when rejecting an invite (amongst other actions).Īside from all of that, we want to let you know about some changes on the horizon. For more details see the upgrade notes and our blog post explaining the situation in greater detail. This means that for those admins who want their room directories to be publicly searchable ( for instance) they need to explicitly say so in the config.

Previously it was possible to inadvertently configure the directory to be visible to arbitrary Matrix servers and the internet in general. For more details take a look at the config here ─ it should be pretty self explanatory.Īnother significant change this release is to explicitly set room directories to be private by default. This release includes some long requested features, most notably the ability to automatically delete message data after a predefined period.

Synapse v4 7.0 roblox download