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

Merge 07ea220e6b into 68ffc62de3

Browse source
This commit is contained in:
Kim Brose 2026-06-24 19:32:05 +00:00 committed by GitHub
parent 68ffc62de3 07ea220e6b
commit 11286801ef
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelogs/appendices/newsfragments/2396.clarification Normal file
View file

@ -0,0 +1 @@
Clarify that clients must avoid producing ambiguous matrix.to URIs. Contributed by @HarHarLinks.

11
content/appendices.md
View file

@ -887,20 +887,21 @@ https://matrix.to/#/<identifier>/<extra parameter>?<additional arguments>
The identifier may be a room ID, room alias, or user ID. The The identifier may be a room ID, room alias, or user ID. The
extra parameter is only used in the case of permalinks where an event ID extra parameter is only used in the case of permalinks where an event ID
is referenced. The matrix.to URI, when referenced, must always start is referenced. The matrix.to URI, when referenced, MUST always start
with `https://matrix.to/#/` followed by the identifier. with `https://matrix.to/#/` followed by the identifier.
The `<additional arguments>` and the preceding question mark are The `<additional arguments>` and the preceding question mark are
optional and only apply in certain circumstances, documented below. OPTIONAL and only apply in certain circumstances, documented below.
Clients should not rely on matrix.to URIs falling back to a web server Clients SHOULD NOT rely on matrix.to URIs falling back to a web server
if accessed and instead should perform some sort of action within the if accessed and instead SHOULD perform some sort of action within the
client. For example, if the user were to click on a matrix.to URI for a client. For example, if the user were to click on a matrix.to URI for a
room alias, the client may open a view for the user to participate in room alias, the client MAY open a view for the user to participate in
the room. the room.
The components of the matrix.to URI (`<identifier>` and The components of the matrix.to URI (`<identifier>` and
`<extra parameter>`) MUST be percent-encoded as per RFC 3986. `<extra parameter>`) MUST be percent-encoded as per RFC 3986.
Clients MUST NOT produce incorrectly encoded URIs to avoid ambiguous interpretation.
Examples of matrix.to URIs are: Examples of matrix.to URIs are: