Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-23 19:44:09 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Use spec-proposals repo for links in spec text and current changelog

Browse source
This commit is contained in:
Travis Ralston 2022-05-05 15:39:31 -06:00
parent 2997c9089d
commit 8cd7deacd3
4 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
changelogs/client_server/newsfragments/1002.feature
View file

@ -1 +1 @@
Make `from` optional on `GET /_matrix/client/v3/messages` to allow requesting events from the start or end of the room history, as per [MSC3567](https://github.com/matrix-org/matrix-doc/pull/3567). Make `from` optional on `GET /_matrix/client/v3/messages` to allow requesting events from the start or end of the room history, as per [MSC3567](https://github.com/matrix-org/matrix-spec-proposals/pull/3567).

2
content/client-server-api/_index.md
View file

@ -1490,7 +1490,7 @@ before using the contents verbatim.
**It is not safe to assume that an event body will have all the expected **It is not safe to assume that an event body will have all the expected
fields of the expected types.** fields of the expected types.**
See [MSC2801](https://github.com/matrix-org/matrix-doc/pull/2801) for more See [MSC2801](https://github.com/matrix-org/matrix-spec-proposals/pull/2801) for more
detail on why this assumption is unsafe. detail on why this assumption is unsafe.
{{% /boxes/warning %}} {{% /boxes/warning %}}

2
content/client-server-api/modules/instant_messaging.md
View file

@ -102,7 +102,7 @@ the tag entirely.
{{% boxes/note %}} {{% boxes/note %}}
A future iteration of the specification will support more powerful and A future iteration of the specification will support more powerful and
extensible message formatting options, such as the proposal extensible message formatting options, such as the proposal
[MSC1767](https://github.com/matrix-org/matrix-doc/pull/1767). [MSC1767](https://github.com/matrix-org/matrix-spec-proposals/pull/1767).
{{% /boxes/note %}} {{% /boxes/note %}}
{{% msgtypes %}} {{% msgtypes %}}

6
content/client-server-api/modules/moderation_policies.md
View file

@ -53,7 +53,7 @@ follows:
- Is a `room` rule... - Is a `room` rule...
- Applied to a user: The user should leave the room and not join - Applied to a user: The user should leave the room and not join
it it
([MSC2270](https://github.com/matrix-org/matrix-doc/pull/2270)-style ([MSC2270](https://github.com/matrix-org/matrix-spec-proposals/pull/2270)-style
ignore). ignore).
- Applied to a room: No-op because a room cannot ban itself. - Applied to a room: No-op because a room cannot ban itself.
- Applied to a server: The server should prevent users from - Applied to a server: The server should prevent users from
@ -120,6 +120,6 @@ Depending on how implementations handle subscriptions, user IDs may be
linked to policy lists and therefore expose the views of that user. For linked to policy lists and therefore expose the views of that user. For
example, a client implementation which joins the user to the policy room example, a client implementation which joins the user to the policy room
would expose the user's ID to observers of the policy room. In future, would expose the user's ID to observers of the policy room. In future,
[MSC1228](https://github.com/matrix-org/matrix-doc/pulls/1228) and [MSC1228](https://github.com/matrix-org/matrix-spec-proposals/pulls/1228) and
[MSC1777](https://github.com/matrix-org/matrix-doc/pulls/1777) (or [MSC1777](https://github.com/matrix-org/matrix-spec-proposals/pulls/1777) (or
similar) could help solve this concern. similar) could help solve this concern.