Skip to content

Issues: matrix-org/matrix-spec

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
297 Open 112 Closed
297 Open 112 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

MXC sanitising spec is unclear/impossible to apply clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1992 opened Nov 11, 2024 by richvdh
3
Example test cases for common edge cases in state resolution clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1989 opened Nov 6, 2024 by CobaltCause
How does signature verification work in pre-v6 rooms clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1988 opened Nov 5, 2024 by Benjamin-L
5
Clarify order of initial vs incremental /sync clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1917 opened Aug 5, 2024 by MadLittleMods
Setting power levels during room creation clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1901 opened Jul 5, 2024 by Johennes
2
Unclear requirements of where canonical JSON must be enforced clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1898 opened Jul 4, 2024 by CobaltCause
Rate-limiting behaviour is not well-defined for clients in the Client-Server API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1889 opened Jun 25, 2024 by reivilibre
Pre-filtering load limits are not discussed in the spec clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1887 opened Jun 25, 2024 by Benjamin-L
"Requires authentication" phrasing can be confusing clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1878 opened Jun 18, 2024 by zecakeh
All APIs should have a dedicated "Unsupported Endpoints" section clarification An area where the expected behaviour is understood, but the spec could do with being more explicit good first issue This is a fix that might be an easy place for someone to start for their first contribution
#1815 opened May 3, 2024 by turt2live
1
/turnServer doesn't specify error when homeserver has no TURN server clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1795 opened Apr 17, 2024 by Kladki
1
Clarify how implementations of federation /send are to apply Server Access Control Lists on a "per PDU basis" clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1784 opened Apr 12, 2024 by Gnuxie
5
Use RFC 2119 keywords consistently clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1782 opened Apr 10, 2024 by turt2live
9
It's not clear whether /versions should fail if auth is invalid A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1779 opened Apr 7, 2024 by Kladki
1
4
Clarification of invite->knock introduced in 1.10 should be at least a warning on older rendered spec versions clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1777 opened Apr 3, 2024 by MTRNord
2
Behaviour of allow_remote on media endpoints is unclear A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit good first issue This is a fix that might be an easy place for someone to start for their first contribution
#1767 opened Mar 22, 2024 by deepbluev7
1
/media/v3/preview_url response spec should include more properties A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1753 opened Mar 19, 2024 by cperrin88
6
SSSS passphrase encoding clarification An area where the expected behaviour is understood, but the spec could do with being more explicit good first issue This is a fix that might be an easy place for someone to start for their first contribution
#1750 opened Mar 13, 2024 by KitsuneRal
1
Threaded receipt EDU shape down /sync makes it impossible to express certain valid receipts A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1727 opened Feb 15, 2024 by kegsay
8
/_matrix/key/v2/server says it's signed by "the verify keys", but which ones from the list should be used? A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit good first issue This is a fix that might be an easy place for someone to start for their first contribution
#1726 opened Feb 15, 2024 by turt2live
2
'Third-party Signed' object does not say who the signatures are supposed to be from or why they are there A-3PID Issues affecting third-party identifiers and invites A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1722 opened Feb 2, 2024 by reivilibre
It's unclear what OpenID standard is actually meant by 'OpenID', if any at all clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1691 opened Dec 5, 2023 by reivilibre
3
Spec incorrectly claims that state events are *overwritten* clarification An area where the expected behaviour is understood, but the spec could do with being more explicit good first issue This is a fix that might be an easy place for someone to start for their first contribution
#1686 opened Dec 1, 2023 by OSto-git-ut
1
6
The limited flag in Timeline in /sync response needs clarification A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1664 opened Oct 19, 2023 by erikjohnston
1
Spec incorrectly states that lang field in response to /pushers is required A-Client-Server Issues affecting the CS API A-Push clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1643 opened Sep 21, 2023 by nico-famedly
4
ProTip! Exclude everything labeled bug with -label:bug.