From 2fb7ce82d20d4213e82d64353ea39bebc5cfa0f2 Mon Sep 17 00:00:00 2001 From: Andrew Morgan Date: Fri, 4 Aug 2023 10:18:58 +0100 Subject: [PATCH] fix duplicated content now how did that happen --- data/api/client-server/report_content.yaml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/data/api/client-server/report_content.yaml b/data/api/client-server/report_content.yaml index 41ac3669..ee7caa63 100644 --- a/data/api/client-server/report_content.yaml +++ b/data/api/client-server/report_content.yaml @@ -35,12 +35,6 @@ paths: the appropriate people. The caller must be joined to the room to report it. - It can be possible for clients to deduce whether an event exists by - timing the response, as only a report for an event that does exist - will require the homeserver to check whether a user is joined to - the room. To combat this, homeserver implementations are encouraged - to add a random delay when generating the response. - It might be possible for clients to deduce whether an event exists by timing the response, as only a report for an event that does exist will require the homeserver to check whether a user is joined to @@ -97,9 +91,6 @@ paths: Homeserver implementations can additionally return this error if the reported event has been redacted. - - Homeserver implementations may additionally return this error if the - reported event has been redacted. examples: application/json: { "errcode": "M_NOT_FOUND",