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

1,068 Open 407 Closed
1,068 Open 407 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

Document the actual current implementation requirements of the MSC process spec-bug Something which is in the spec, but is wrong
#2058 opened Jan 15, 2025 by HarHarLinks
2
id_server format is not documented clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2056 opened Jan 15, 2025 by zecakeh
https://spec.matrix.org/proposals/ has broken/no CSS aesthetic A suggestion or issue relating to the representation of the spec
#2054 opened Jan 15, 2025 by turt2live
3
Missing knock->join transition on membership transition graph and table spec-bug Something which is in the spec, but is wrong
#2053 opened Jan 14, 2025 by richvdh
/directory/room{roomAlias} leaks all involved homeservers clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2052 opened Jan 14, 2025 by stefanceriu
1
origin_client_ts to distinguish composed v. sent timestamps improvement An idea/future MSC for the spec
#2043 opened Dec 28, 2024 by ara4n
Secret storage section needs cleanup clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2040 opened Dec 19, 2024 by richvdh
Upgrade CI actions meta Something that is not a spec change/request and is not related to the build tools
#2039 opened Dec 19, 2024 by turt2live
v11 auth rules 2.2 is unclear in combination with auth event selection algo clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2035 opened Dec 17, 2024 by dkasak
What is the point of /keys/changes ? clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2034 opened Dec 16, 2024 by richvdh
1
How about a message type which will never trigger notifications? improvement An idea/future MSC for the spec
#2031 opened Dec 14, 2024 by rowskilled14
Account data section needs cleanup 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 help wanted Interested in contributing to the spec? These would be great additions!
#2030 opened Dec 13, 2024 by richvdh
1
Should v3+ room version events containing an event_id field be rejected? clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2027 opened Dec 9, 2024 by anoadragon453
6
State events from blocked users should not be shown to clients improvement An idea/future MSC for the spec
#2025 opened Dec 5, 2024 by everypizza1
3
ETag support for /_matrix/client/v3/rooms/{roomId}/state improvement An idea/future MSC for the spec
#2020 opened Nov 29, 2024 by Half-Shot
Ability to specify a filter for /_matrix/client/v3/rooms/{roomId}/state improvement An idea/future MSC for the spec
#2019 opened Nov 29, 2024 by Half-Shot
[Brainstorming] More granular access controls/power levels improvement An idea/future MSC for the spec
#2012 opened Nov 25, 2024 by TheArcaneBrony
4
Clarify when state_key needs to be "" in authorization rules clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1998 opened Nov 15, 2024 by CobaltCause
5
Spec text incorrectly renders query parameters of type object clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1993 opened Nov 12, 2024 by richvdh
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
C-S API MXC Security Consideration pretty much all MXCs are invalid spec-bug Something which is in the spec, but is wrong
#1990 opened Nov 7, 2024 by t3chguy
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 olivia-fl
5
Should we do away with 4S secret storage in favour of deriving everything deterministically from the recovery key? improvement An idea/future MSC for the spec
#1987 opened Nov 1, 2024 by dkasak
Lazy load text has inconsistent url parameter notation spec-bug Something which is in the spec, but is wrong
#1982 opened Oct 17, 2024 by MTRNord
2
ProTip! Find all open issues with in progress development work with linked:pr.