Add blog post for Synapse 1.72/71/70

gatsby/content/blog/2022/11/2022-11-22-synapse-1.72.mdx

@@ -0,0 +1,70 @@
+---
+date: '2022-11-18'
+title: Synapse 1.72 released
+categories:
+- Releases
+author: Mathieu Velten
+---
+
+It's not yet Christmas, but it's time for a new release! Say hello to [Synapse 1.72](https://github.com/matrix-org/synapse/releases/tag/v1.72.0).
+
+It seems like this blog didn't self update through AI for the 2 precedent updates so this post will cover 1.70 to 1.72, sorry if this is a bit long but it's been a while :)
+
+## Announcements
+
+### Dropping support for PostgreSQL 10
+
+PostgreSQL 10 being End Of Life, Synapse will not support it beginning with version 1.72 so please upgrade your DB if not already done.
+
+### Legacy Prometheus metric names disabled and to be removed
+
+In previous versions of Synapse, some Prometheus metrics are emitted under two different names, with one of the names being older but non-compliant with OpenMetrics and Prometheus conventions and one of the names being newer but compliant.
+
+Synapse v1.71 have the old metric names switched off by default.
+
+For now it's still possible to get them by using `enable_legacy_metrics: true`, however if you still use them you should really migrate because it will be removed in v1.73.
+
+You can find the full list of renamed metrics [here](https://matrix-org.github.io/synapse/v1.69/metrics-howto.html#renaming-of-metrics--deprecation-of-old-names-in-12).
+
+### Changes to the events received by application services (interest)
+
+[MSC3905](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3905-appservice-only-interested-in-local-users.md) has been implemented, Synapse now only considers local users to be interesting. In other words, the users namespace regex is only be applied against local users of the homeserver.
+
+Please note, this probably doesn't affect the expected behavior of your application service, since an interesting local user in a room still means all messages in the room (from local or remote users) will still be considered interesting.
+
+You can find a bit more info in the MSC and in the (upgrade notes)[https://matrix-org.github.io/synapse/v1.71/upgrade.html#changes-to-the-events-received-by-application-services-interest].
+
+## The new stuffs
+
+### Threads, threads, threads!
+
+Several MSCs related to threads got implemented:
+- [MSC3856](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3856-threads-list-api.md) providing an API to fetch threads and related metadata.
+- [MSC3771](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3771-read-receipts-for-threads.md) and [MSC3773](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3773-notifications-for-threads.md) implementing per thread read receipts and per thread notifications count.
+- [MSC3874](https://github.com/matrix-org/matrix-spec-proposals/blob/justjanne/messages-endpoint-threads-filter/proposals/3874-messages-endpoint-threads-filter.md) allows to filter out messages belonging to threads from the main timeline. Along with MSC3856, this should noticeably improve performance of rooms that use threads heavily.
+
+This should significantly improve user experience related to threads, being through behavior or performance impact.
+
+### Bounding events together
+
+Relationships are great, even more between events than humans!
+
+[MSC3912](https://github.com/matrix-org/matrix-spec-proposals/blob/babolivier/relation_redaction/proposals/3912-relation-based-redaction.md) gives us an easy way to redact an event with its relations of a certain type.
+For example it's usually good practice to redact all the edited versions of a message. Beforehand this work would have been done one event at a time by the client itself, now you can just specify relation types you want to delete in `with_relations` and the server will take care of that for you!
+
+[MSC3664](https://github.com/deepbluev7/matrix-doc/blob/notifications-for-relations/proposals/3664-notifications-for-relations.md) allows Matrix clients to be notified in real time of related events, so you can now be made quickly aware of this cat emoji reaction that your cat photo clearly deserved.
+
+### Faster joins, continued
+
+We continue our journey to get everything going as transparently as possible when doing fast remote room joins.
+
+If you missed it you can refer to this previous [blog post](https://matrix.org/blog/2022/10/18/testing-faster-remote-room-joins) to get a lot more infos,
+and feel free to grep Synapse changelog and the numerous related issues/PRs for all the gory details.
+
+TODO Synapse is a Free and Open Source Software project, and we'd like to extend our
+thanks to everyone who contributed to this release, including (in no particular
+order) [Denis Kariakin](https://github.com/dakariakin), [Dirk
+Klimpel](https://github.com/dklimpel) and [Beeper](https://www.beeper.com/), as
+well as anyone helping us make Synapse better by sharing their feedback and
+reporting issues.
+