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,060 Open 357 Closed
1,060 Open 357 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

Deprecate query string authorization for /_matrix/federation/v1/openid/userinfo improvement An idea/future MSC for the spec
#1902 opened Jul 5, 2024 by Johennes
1
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
Fallback login spec doesn't specify what arguments onLogin takes (if any) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1900 opened Jul 5, 2024 by Johennes
1
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
1
Behaviour of restricted rooms with no valid conditions is not clear clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1891 opened Jun 27, 2024 by Kladki
2
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
2
How should an appservice opt-out of providing an endpoint?
#1859 opened Jun 11, 2024 by Half-Shot
4
/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
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
/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
1
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
ProTip! Type g i on any issue or pull request to go back to the issue listing page.