Compare commits

..

1 commit

Author SHA1 Message Date
Johannes Marbach ef9f6ae22a Spec for MSC4312: Resetting cross-signing keys in the OAuth world
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
2025-10-17 14:45:54 +02:00
6 changed files with 4 additions and 11 deletions

View file

@ -1 +0,0 @@
Fix various typos throughout the specification.

View file

@ -1 +0,0 @@
Add `m.login.terms` to enumeration of authentication types.

View file

@ -1 +0,0 @@
Silence failing redocly-cli rule.

View file

@ -906,7 +906,6 @@ This specification defines the following auth types:
- `m.login.msisdn` - `m.login.msisdn`
- `m.login.dummy` - `m.login.dummy`
- `m.login.registration_token` - `m.login.registration_token`
- {{% added-in v="1.11" %}} `m.login.terms`
- {{% added-in v="1.17" %}} `m.oauth` - {{% added-in v="1.17" %}} `m.oauth`
###### Password-based ###### Password-based

View file

@ -20,9 +20,9 @@ Previously, a rich reply could only reference another `m.room.message` event.
{{% boxes/note %}} {{% boxes/note %}}
{{% changed-in v="1.13" %}} {{% changed-in v="1.13" %}}
In previous versions of the specification, rich replies could include a fallback In previous versions of the specification, rich replies could include a fallback
representation of the original message in the `body` (using a prefix sequence) representation of the original message message in the `body` (using a prefix
and `formatted_body` (using a custom HTML element) for clients that do not sequence) and `formatted_body` (using a custom HTML element) for clients that do
support rich replies. This is no longer the case, but clients SHOULD still not support rich replies. This is no longer the case, but clients SHOULD still
remove this fallback before rendering the event. remove this fallback before rendering the event.
To strip the fallback on the `body`, the client should iterate over each To strip the fallback on the `body`, the client should iterate over each

View file

@ -8,7 +8,4 @@ rules:
no-invalid-media-type-examples: off no-invalid-media-type-examples: off
no-path-trailing-slash: off no-path-trailing-slash: off
operation-2xx-response: off operation-2xx-response: off
spec-strict-refs: error spec-strict-refs: error
# $ref in examples are not spec-compliant, yet we find them useful. Disable this rule
# and instead check example schema using `check-event-schema-examples.py`
no-invalid-schema-examples: off