Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-04 21:33:42 +01:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Add an unstable feature flag to MSC2140 for clients to detect support

Browse source
This commit is contained in:
Travis Ralston 2019-08-29 13:59:48 -06:00
parent 03641d9e48
commit 16bb3bd8b5
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
proposals/2140-terms-of-service-2.md
View file

@ -170,7 +170,7 @@ This endpoint does *not* require authentication.
#### `POST $prefix/terms`:
Requests to this endpoint have a single key, `user_accepts` whose value is
a list of URLs (given by the `url` field in the GET response) of documents that
a list of URLs (given by the `url` field in the GET response) of documents that
the user has agreed to:
```json
@ -277,6 +277,16 @@ Clients may add IS bindings for 3PIDs that already exist on the user's
Homeserver account by using the `POST /_matrix/client/r0/account/3pid`
to re-add the 3PID.
### Unstable feature flag for transition
In order to allow client implementations to determine if the homeserver they are developed
against supports `id_access_token`, an unstable feature flag of `m.id_access_token`
is to be added to `/versions`. When the flag is `false` or not present, clients must assume
that the homeserver does not support being given `id_access_token` and may receive an error
for doing so. Clients are expected to use the supported specification versions the homeserver
advertises instead of the feature flag's presence once this proposal is included in a release
of the specification.
## Tradeoffs
The Identity Service API previously did not require authentication, and OpenID