From 6b992283866c8bbcb32c577561631466b758df87 Mon Sep 17 00:00:00 2001 From: Andrew Morgan Date: Thu, 1 Oct 2020 17:25:19 +0100 Subject: [PATCH] Remove section duplicated by membership change section --- proposals/2403-knock.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/proposals/2403-knock.md b/proposals/2403-knock.md index 8fe96eda..da1d135e 100644 --- a/proposals/2403-knock.md +++ b/proposals/2403-knock.md @@ -300,14 +300,6 @@ Response: } ``` -Once a knock has been made, a user in the room can decide whether they want -to accept or deny the knock. If they accept, they will invite the knocker, -which the knocker will be notified about through existing flows. - -If they deny, then a leave membership event is sent in the room, and the -knocking user will be notified through existing flows (matching the behaviour -of when an invite is recinded). - ## Server-Server API Similarly to join and leave over federation, a ping-pong game with two new endpoints is introduced: `make_knock` and `send_knock`. Both endpoints must