Merge 47cce0ca26 into fe3f43a905

changelogs/client_server/newsfragments/2240.clarification

@@ -1 +0,0 @@
-Clarify how to use `state_after` ahead of declaring full support for its spec version.

data/api/client-server/sync.yaml

@@ -133,15 +133,10 @@ paths:
             sync and the **start** of the timeline in `state` and MUST omit
             `state_after`.
 
-            Servers MAY implement this parameter ahead of declaring support for
-            the version of the spec in which it was introduced. Consequently,
-            clients MAY set this parameter to `true` regardless of the
-            [`/versions`](/client-server-api/#get_matrixclientversions) response.
-            If they do, they can infer whether the server actually supports this
-            parameter from the presence of `state_after` in the response. If
-            `state_after` is missing, clients MUST behave as if they had not
-            specified the parameter and update their local state with events
-            in `state` and `timeline`.
+            Even if this is set to `true`, clients MUST update their local state
+            with events in `state` and `timeline` if `state_after` is missing in
+            the response, for compatibility with servers that don't support this
+            parameter.
 
             By default, this is `false`.
           example: false