From 218b86d6e8c6502fa8ccf286358aa1304d282ee9 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Fri, 31 Aug 2018 15:48:41 -0600 Subject: [PATCH] Hopefully the last one --- specification/modules/third_party_invites.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/modules/third_party_invites.rst b/specification/modules/third_party_invites.rst index 9a9391430..df71d2154 100644 --- a/specification/modules/third_party_invites.rst +++ b/specification/modules/third_party_invites.rst @@ -215,7 +215,7 @@ H1 MUST verify the request from H3 to ensure the ``signed`` property is correct as well as the ``key_validity_url`` as still being valid. This is done by making a request to the `identity server /isvalid`_ endpoint, using the provided URL rather than constructing a new one. The query string and response for the provided -URL must match the identity service specification. +URL must match the Identity Service Specification. The reason that no other homeserver may reject the event based on checking ``key_validity_url`` is that we must ensure event acceptance is deterministic.