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,064 Open 393 Closed
1,064 Open 393 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

Matrix 1.13 release-blocker Blocks the next release from happening
#2013 opened Nov 26, 2024 by turt2live
16 tasks
[Brainstorming] More granular access controls/power levels improvement An idea/future MSC for the spec
#2012 opened Nov 25, 2024 by TheArcaneBrony
4
Clarify when state_key needs to be "" in authorization rules clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1998 opened Nov 15, 2024 by CobaltCause
1
Spec text incorrectly renders query parameters of type object clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1993 opened Nov 12, 2024 by richvdh
MXC sanitising spec is unclear/impossible to apply clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1992 opened Nov 11, 2024 by richvdh
3
C-S API MXC Security Consideration pretty much all MXCs are invalid spec-bug Something which is in the spec, but is wrong
#1990 opened Nov 7, 2024 by t3chguy
Example test cases for common edge cases in state resolution clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1989 opened Nov 6, 2024 by CobaltCause
How does signature verification work in pre-v6 rooms clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1988 opened Nov 5, 2024 by Benjamin-L
5
Should we do away with 4S secret storage in favour of deriving everything deterministically from the recovery key? improvement An idea/future MSC for the spec
#1987 opened Nov 1, 2024 by dkasak
Lazy load text has inconsistent url parameter notation spec-bug Something which is in the spec, but is wrong
#1982 opened Oct 17, 2024 by MTRNord
2
Ability to ignore individual messages. improvement An idea/future MSC for the spec
#1981 opened Oct 15, 2024 by ara4n
A Channel Feature Similar to Telegram Channels improvement An idea/future MSC for the spec
#1965 opened Oct 9, 2024 by 0x002500
Historical spec artifacts starting with v1.11 have broken CSS aesthetic A suggestion or issue relating to the representation of the spec release-blocker Blocks the next release from happening
#1964 opened Oct 7, 2024 by turt2live
5
Add some sort of approval step before a new user can send images improvement An idea/future MSC for the spec
#1963 opened Oct 6, 2024 by ell1e
1
Reuse Invite3pid object across spec aesthetic A suggestion or issue relating to the representation of the spec
#1955 opened Sep 30, 2024 by td-famedly
3
Divide thread and messages permissions improvement An idea/future MSC for the spec
#1953 opened Sep 28, 2024 by Jlucu4ka228
1
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
1
createRoom should be atomic improvement An idea/future MSC for the spec
#1951 opened Sep 17, 2024 by nico-famedly
4
Distinction between deleting devices and invalidating access tokens is bogus and confusing improvement An idea/future MSC for the spec
#1950 opened Sep 13, 2024 by dkasak
Authenticated Media v2 improvement An idea/future MSC for the spec
#1949 opened Sep 12, 2024 by dbkr
15
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
1
m.room.power_levels provide no way of restricting the media (via mixins) you can embed into events. improvement An idea/future MSC for the spec
#1932 opened Aug 16, 2024 by Gnuxie
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
3
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
Should we be descriptive or prescriptive about how room upgrades work?
#1906 opened Jul 8, 2024 by turt2live
ProTip! Exclude everything labeled bug with -label:bug.