From 60dd9231e0ff0114a04ad9f5666ba7527b025164 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Fri, 31 Aug 2018 11:26:28 -0600 Subject: [PATCH] Don't explain how the IS might accept a 3pid The IS is bound to it's own set of specifications, and if the client chose this API then they should be aware of the risks but not necessarily arbitrary alternatives. --- api/client-server/administrative_contact.yaml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/api/client-server/administrative_contact.yaml b/api/client-server/administrative_contact.yaml index d2594c95..0fdbf742 100644 --- a/api/client-server/administrative_contact.yaml +++ b/api/client-server/administrative_contact.yaml @@ -218,8 +218,7 @@ paths: 403: description: |- The homeserver does not permit the user from having the third party - identifier as a contact option. This does not prevent the identity - service from binding the third party identifier, however. + identifier as a contact option. schema: $ref: "definitions/errors/error.yaml" examples: @@ -273,8 +272,7 @@ paths: 403: description: |- The homeserver does not permit the user from having the third party - identifier as a contact option. This does not prevent the identity - service from binding the third party identifier, however. + identifier as a contact option. schema: $ref: "definitions/errors/error.yaml" examples: