From 5c96969c724a7776da492f7c02fdda54f27b6de5 Mon Sep 17 00:00:00 2001 From: giomfo Date: Wed, 10 Jan 2024 17:54:51 +0100 Subject: [PATCH] Update proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- .../4028-push-all-encrypted-events-except-for-muted-rooms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md b/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md index df32988c..4931044c 100644 --- a/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md +++ b/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md @@ -233,7 +233,7 @@ During development the new push rule shall use `org.matrix.msc4028.encrypted_eve Caution: this unstable push rule will be enabled by default like the stable push rule, the server owners should wait for the clients to support a minimum this MSC before enabling the MSC server side. -To ensure the server supports the functionality before a spec release, clients should look for the unstable feature `org.matrix.msc4028` in the response of the `/_matrix/clients/versions` endpoint. Once released in the specification, clients should be checking for server support through advertised spec versions instead. +To ensure the server supports the functionality before a spec release, clients should interpret an unstable feature `org.matrix.msc4028` with a value of `true` in the response of the `/_matrix/clients/versions` endpoint as the feature being supported by the homeserver. Once released in the specification, clients should be checking for server support through advertised spec versions instead. Once this MSC has successfully passed a merge FCP, clients should use `.m.rule.encrypted_event` as the right push rule. The unstable `org.matrix.msc4028.encrypted_event` can be used only as a fallback if the right one is missing (backwards compatibility with slightly old servers).