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.

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

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

Issues list

Federated media multipart/mixed JSON object shouldn't be required to be empty spec-bug Something which is in the spec, but is wrong
#1952 opened Sep 18, 2024 by f0x52
createRoom should be atomic improvement An idea/future MSC for the spec
#1951 opened Sep 17, 2024 by nico-famedly
Authenticated Media v2 improvement An idea/future MSC for the spec
#1949 opened Sep 12, 2024 by dbkr
Clarify notary servers are no longer required to sign responses improvement An idea/future MSC for the spec
#1948 opened Sep 12, 2024 by f0x52
Text calling improvement An idea/future MSC for the spec
#1925 opened Aug 11, 2024 by Feliks-WR
Make state resolution faster A-Room-spec Something to do with the room version specifications improvement An idea/future MSC for the spec room-vNext An idea which will require a bump in room version
#1922 opened Aug 9, 2024 by alexeyshch
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
Servers don't enforce PDU format
#1904 opened Jul 7, 2024 by Kladki
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
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
Allow read markers to go backwards A-Push improvement An idea/future MSC for the spec
#1893 opened Jul 1, 2024 by nunoperalta
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
Consider adopting the Apache voting scale for FCP meta Something that is not a spec change/request and is not related to the build tools
#1879 opened Jun 18, 2024 by turt2live
"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
Handlebars spills through into API viewer aesthetic A suggestion or issue relating to the representation of the spec
#1873 opened Jun 17, 2024 by KitsuneRal
/logout does not take a request body, which is inconsistent wart A point where the protocol is inconsistent or inelegant
#1845 opened Jun 5, 2024 by reivilibre
Collapsible sections in the table-of-contents aesthetic A suggestion or issue relating to the representation of the spec
#1825 opened May 21, 2024 by opk12
ProTip! Follow long discussions with comments:>50.