From 65eb30b49142acfb776fc6d0b7ad1c1061663403 Mon Sep 17 00:00:00 2001 From: Tulir Asokan Date: Sun, 21 Sep 2025 15:10:44 +0300 Subject: [PATCH] Switch error code to M_UNKNOWN_DEVICE --- proposals/4326-appservice-device-masquerading.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/proposals/4326-appservice-device-masquerading.md b/proposals/4326-appservice-device-masquerading.md index 4ffa948af..a1b9c53c6 100644 --- a/proposals/4326-appservice-device-masquerading.md +++ b/proposals/4326-appservice-device-masquerading.md @@ -21,7 +21,7 @@ details for the remainder of the request. For many endpoints this means updating and "last seen timestamp" for the device, though for some endpoints it may mean interacting with the device specifically (such as when uploading one-time keys). -If the `device_id` does not already exist on the `user_id`, the server returns a `400 M_EXCLUSIVE` +If the `device_id` does not already exist on the `user_id`, the server returns a `400 M_UNKNOWN_DEVICE` standard error response. If the `device_id` is present without a `user_id`, the `user_id` is assumed to be the appservice's @@ -110,6 +110,7 @@ they could log out whatever devices they don't want and register new ones accord For historical reasons, unstable implementations of this proposal should use `org.matrix.msc3202.device_id` instead of `device_id`. +`ORG.MATRIX.MSC4326.M_UNKNOWN_DEVICE` is used as the error code instead of `M_UNKNOWN_DEVICE`. ## Dependencies