From aa87ba91fd09ec0d605ae51a8b48b0f534c281e0 Mon Sep 17 00:00:00 2001 From: Brendan Abolivier Date: Fri, 12 Aug 2022 17:10:17 +0100 Subject: [PATCH] MSC number --- ...-not-approved-error.md => 3866-user-not-approved-error.md} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename proposals/{XXXX-user-not-approved-error.md => 3866-user-not-approved-error.md} (97%) diff --git a/proposals/XXXX-user-not-approved-error.md b/proposals/3866-user-not-approved-error.md similarity index 97% rename from proposals/XXXX-user-not-approved-error.md rename to proposals/3866-user-not-approved-error.md index 822f65d33..77fd37f26 100644 --- a/proposals/XXXX-user-not-approved-error.md +++ b/proposals/3866-user-not-approved-error.md @@ -1,4 +1,4 @@ -# MSCXXXX: `M_USER_NOT_APPROVED` error code +# MSC3866: `M_USER_NOT_APPROVED` error code Over the past few years, there has been some demand for the ability to let administrators of homeservers approve any new user created on their homeserver @@ -86,5 +86,5 @@ they've been approved) or a server administrator generated one for them). ## Unstable prefix -During development, `ORG_MATRIX_MSCXXXX_USER_NOT_APPROVED` must be used instead +During development, `ORG_MATRIX_MSC3866_USER_NOT_APPROVED` must be used instead of `M_USER_NOT_APPROVED`.