Skip to content

Issues: matrix-org/matrix-spec

Matrix 1.11
#1857 opened Jun 10, 2024 by turt2live
Open
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,061 Open 341 Closed
1,061 Open 341 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
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

How should an appservice opt-out of providing an endpoint?
#1859 opened Jun 11, 2024 by Half-Shot
2
Matrix 1.11 release-blocker Blocks the next release from happening
#1857 opened Jun 10, 2024 by turt2live
1 of 13 tasks
@turt2live
/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
1
GET /client/publicRooms is marked as not requiring auth, despite Synapse requiring it by default.
#1835 opened Jun 1, 2024 by Kladki
2
Clarify Room ID requirements clarification An area where the expected behaviour is understood, but the spec could do with being more explicit help wanted Interested in contributing to the spec? These would be great additions!
#1826 opened May 23, 2024 by HarHarLinks
1
5
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
1
Seperate space permissions for adding and removing rooms improvement An idea/future MSC for the spec
#1821 opened May 13, 2024 by eickeh
auth_events and prev_events arrays of v1 PDU are flattened spec-bug Something which is in the spec, but is wrong
#1820 opened May 10, 2024 by Kladki
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
Empty objects and null in registration arrays aesthetic A suggestion or issue relating to the representation of the spec
#1811 opened Apr 30, 2024 by Kladki
POST /_matrix/client/v3/account/password has authentication set as required but description says it is optional spec-bug Something which is in the spec, but is wrong
#1807 opened Apr 26, 2024 by zecakeh
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
Portable identities improvement An idea/future MSC for the spec
#1792 opened Apr 16, 2024 by ara4n
4
anchor tag name attribute is deprectated spec-bug Something which is in the spec, but is wrong
#1790 opened Apr 16, 2024 by HarHarLinks
2
Triage spec issues improvement An idea/future MSC for the spec
#1785 opened Apr 12, 2024 by Gnuxie
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
Provide an error code field to failed PDUs in federation /send similar to http apis improvement An idea/future MSC for the spec
#1783 opened Apr 12, 2024 by Gnuxie
1
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
2
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
Non-interactive E2EE Account Verification improvement An idea/future MSC for the spec
#1778 opened Apr 6, 2024 by kevincox
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
"Added in" and "Changed in" attributes should be rendered when attached to requests and responses A-Tools Related to the process and tools for building the spec clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1774 opened Apr 1, 2024 by turt2live
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
Test building the historical spec more frequently than release cadence A-Tools Related to the process and tools for building the spec spec-bug Something which is in the spec, but is wrong
#1764 opened Mar 22, 2024 by turt2live
/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
ProTip! Updated in the last three days: updated:>2024-06-08.