Skip to content

MSC3012: Post-registration terms of service API#3012

Closed
turt2live wants to merge 1 commit into
old_masterfrom
travis/msc/tos-api
Closed

MSC3012: Post-registration terms of service API#3012
turt2live wants to merge 1 commit into
old_masterfrom
travis/msc/tos-api

Conversation

@turt2live
Copy link
Copy Markdown
Member

@turt2live turt2live added client-server Client-Server API kind:core MSC which is critical to the protocol's success proposal A matrix spec change proposal proposal-in-review labels Feb 17, 2021
Comment thread proposals/3012-tos-api.md
6. The homeserver logs the user in by generating a token and returning it to the client as per
the specification.

This process is chosen to begin introducing the UI auth mechanism to login without breaking clients.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#2835 switches to full UIA directly and does not break login with existing clients. Special-casing terms seems unneeded?

@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
Comment thread proposals/3012-tos-api.md
In addition, the homeserver should not prevent the use of the special "terms acceptance" API
described in the next section.

### Terms acceptance API
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there should also be an (unauthenticated) endpoint to get the current terms, mirroring the identity server approach. Optional authentication for scoping.

@turt2live
Copy link
Copy Markdown
Member Author

Closing - other techniques have been used in practice to accomplish this, like using server notices.

@turt2live turt2live closed this May 14, 2026
@turt2live turt2live added the abandoned A proposal where the author/shepherd is not responsive label May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

abandoned A proposal where the author/shepherd is not responsive client-server Client-Server API kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants