|
|
@ -378,11 +378,14 @@ Content-Type: application/json
|
|
|
|
|
|
|
|
|
|
|
|
#### Response:
|
|
|
|
#### Response:
|
|
|
|
##### Status code 200:
|
|
|
|
##### Status code 200:
|
|
|
|
The event was successfully accepted into the graph by the receiving
|
|
|
|
The event was successfully accepted into the graph by the homeserver that
|
|
|
|
homeserver. The response contains `StrippedStateEvent`s with room metadata
|
|
|
|
received the knock. It must then send this knock into the room, before
|
|
|
|
(room name, avatar ...) that the knocking homeserver can pass to the client.
|
|
|
|
responding to the knocking homeserver, indicating the knock succeeded.
|
|
|
|
The event types that can be sent here should match those of the `/sync`
|
|
|
|
|
|
|
|
extensions mentioned above.
|
|
|
|
The response contains `StrippedStateEvent`s with room metadata (room name,
|
|
|
|
|
|
|
|
avatar ...) that the knocking homeserver can pass to the client. The event
|
|
|
|
|
|
|
|
types that can be sent here should match those of the `/sync` extensions
|
|
|
|
|
|
|
|
mentioned above.
|
|
|
|
|
|
|
|
|
|
|
|
This is loosely based on the
|
|
|
|
This is loosely based on the
|
|
|
|
[federated invite](https://matrix.org/docs/spec/server_server/r0.1.4#put-matrix-federation-v2-invite-roomid-eventid)
|
|
|
|
[federated invite](https://matrix.org/docs/spec/server_server/r0.1.4#put-matrix-federation-v2-invite-roomid-eventid)
|
|
|
|