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,063 Open 422 Closed
1,063 Open 422 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

Unclear IP address syntax requirements clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2090 opened Mar 5, 2025 by CobaltCause
3
Message edits should clear reactions (emoji) to that message - replies should store the timestamp of the referred message improvement An idea/future MSC for the spec
#2089 opened Feb 26, 2025 by aral-matrix
Encrypted attachments V3
#2087 opened Feb 25, 2025 by richvdh
Unclear what a membership event means in the case of changing global profile info clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2086 opened Feb 25, 2025 by TheArcaneBrony
1
Allow appservices to override user capabilites improvement An idea/future MSC for the spec
#2085 opened Feb 25, 2025 by Half-Shot
[Bug] Spec documentation doesn't build with Hugo 0.141+
#2084 opened Feb 25, 2025 by TheArcaneBrony
It is unclear when third_party_signed property of /join endpoints should be used clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2082 opened Feb 22, 2025 by zecakeh
2
Transparency logs for public identity keys improvement An idea/future MSC for the spec
#2075 opened Feb 21, 2025 by richvdh
1
Document that incoming invite events will reach a homeserver twice - once over /invite and again over /send improvement An idea/future MSC for the spec
#2062 opened Jan 24, 2025 by anoadragon453
1
4
Identity servers public_key(s) base64 format needs to be clarified clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2060 opened Jan 21, 2025 by zecakeh
1
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
3
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
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
5
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
ProTip! Type g i on any issue or pull request to go back to the issue listing page.