Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-04-14 07:04:09 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Capitalise on our identifiers

Browse source
This commit is contained in:
David Baker 2019-06-26 14:52:19 +01:00
parent ba7047ce77
commit 4edf826c93
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -45,7 +45,7 @@ This proposal introduces:
* The `m.accepted_terms` section in account data * The `m.accepted_terms` section in account data
This proposal relies on both Integration Managers and Identity Servers being This proposal relies on both Integration Managers and Identity Servers being
able to identity users by their mxid and store the fact that a given mxid has able to identity users by their MXID and store the fact that a given MXID has
indicated that they accept the terms given. Integration Managers already indicated that they accept the terms given. Integration Managers already
identity users in this way by authenticating them using the OpenID endpoint on identity users in this way by authenticating them using the OpenID endpoint on
the Homeserver. This proposal introduces the same mechanism to Identity Servers the Homeserver. This proposal introduces the same mechanism to Identity Servers
@ -221,8 +221,8 @@ A custom HTTP Header was also considered that could be added to assert that the
client agrees to a particular set of terms. We decided against this in favour client agrees to a particular set of terms. We decided against this in favour
of re-using existing primitives that already exist in the Matrix ecosystem. of re-using existing primitives that already exist in the Matrix ecosystem.
Custom HTTP Headers are not used anywhere else within Matrix. This also gives a Custom HTTP Headers are not used anywhere else within Matrix. This also gives a
very simple and natural way for ISes to enforce that users may only bind 3pids very simple and natural way for ISes to enforce that users may only bind 3PIDs
to their own mxids. to their own MXIDs.
This introduces a different way of accepting terms from the client/server API This introduces a different way of accepting terms from the client/server API
which uses User-Interactive Authentication. In the client/server API, the use which uses User-Interactive Authentication. In the client/server API, the use