From de5ae9da4a3cdd0d4867712bbfb101b1c5177b47 Mon Sep 17 00:00:00 2001 From: Half-Shot Date: Thu, 31 Mar 2022 11:15:34 +0100 Subject: [PATCH] Fix link --- proposals/3759-deactivated-user-metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/3759-deactivated-user-metadata.md b/proposals/3759-deactivated-user-metadata.md index eb9a134e4..667adb23c 100644 --- a/proposals/3759-deactivated-user-metadata.md +++ b/proposals/3759-deactivated-user-metadata.md @@ -65,7 +65,7 @@ bridge configuration) it is satisfactory enough. ## Alternatives -[MSC3720])(https://github.com/matrix-org/matrix-spec-proposals/pull/3720) would help in solving this problem, +[MSC3720](https://github.com/matrix-org/matrix-spec-proposals/pull/3720) would help in solving this problem, as services could lookup the status of a user when a leave event comes in and determine the deactivated status. However this comes with two notable drawbacks: