From d59d05187aa24a55db40997e142020456b46bbb5 Mon Sep 17 00:00:00 2001 From: Will Hunt Date: Fri, 15 Apr 2022 20:45:25 +0100 Subject: [PATCH] Reject r0, embrace v1 Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- proposals/2666-get-rooms-in-common.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/2666-get-rooms-in-common.md b/proposals/2666-get-rooms-in-common.md index 1ecc06323..a00434b73 100644 --- a/proposals/2666-get-rooms-in-common.md +++ b/proposals/2666-get-rooms-in-common.md @@ -30,7 +30,7 @@ Additionally, a server may respond with a `400` `M_UNKNOWN` to this endpoint for signalling its unwillingess (or inability) to satisfy the request. ``` -GET /_matrix/client/r0/user/mutual_rooms/%40bob%3Aexample.com +GET /_matrix/client/v1/user/mutual_rooms/%40bob%3Aexample.com ``` ```json @@ -77,5 +77,5 @@ to request all state ahead of time. The implementation MUST use `/_matrix/client/unstable/uk.half-shot.msc2666/user/mutual_rooms/{user_id}`. The /versions endpoint MUST include a new key in `unstable_features` with the name `uk.half-shot.msc2666.mutual_rooms`. If the value is false or the key is not present, clients MUST assume the feature is not available. -Once the MSC has been merged, clients should use `/_matrix/client/r0/user/mutual_rooms/{user_id}` +Once the MSC has been merged, clients should use `/_matrix/client/v1/user/mutual_rooms/{user_id}` and will no longer need to check for the `unstable_features` flag.