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
Label
Projects
Milestones
Assignee
Sort
Issues list
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
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
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
#1807
opened Apr 26, 2024 by
zecakeh
/turnServer
doesn't specify error when homeserver has no TURN server
clarification
#1795
opened Apr 17, 2024 by
Kladki
a
nchor tag name
attribute is deprectated
spec-bug
#1790
opened Apr 16, 2024 by
HarHarLinks
Clarify how implementations of federation An area where the expected behaviour is understood, but the spec could do with being more explicit
/send
are to apply Server Access Control Lists on a "per PDU basis"
clarification
#1784
opened Apr 12, 2024 by
Gnuxie
Provide an error code field to failed PDUs in federation An idea/future MSC for the spec
/send
similar to http apis
improvement
#1783
opened Apr 12, 2024 by
Gnuxie
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
It's not clear whether Issues affecting the CS API
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
/versions
should fail if auth is invalid
A-Client-Server
#1779
opened Apr 7, 2024 by
Kladki
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
"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 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
allow_remote
on media endpoints is unclear
A-Client-Server
#1767
opened Mar 22, 2024 by
deepbluev7
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
#1753
opened Mar 19, 2024 by
cperrin88
Push Notifications: Add Support for: VAPID / WebPush Subscriptions
A-Push
improvement
An idea/future MSC for the spec
#1752
opened Mar 19, 2024 by
AdamBien
SSSS passphrase encoding
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
#1750
opened Mar 13, 2024 by
KitsuneRal
As a user or appservice, I want to know if another user has access to a specific event.
A-Application-Services
Issues affecting the AS API
A-Client-Server
Issues affecting the CS API
improvement
An idea/future MSC for the spec
#1747
opened Mar 12, 2024 by
Half-Shot
New transport protocol (sunsetting JSON)
improvement
An idea/future MSC for the spec
#1736
opened Feb 29, 2024 by
Saiv46
Threaded receipt EDU shape down /sync makes it impossible to express certain valid receipts
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
#1727
opened Feb 15, 2024 by
kegsay
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.