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,062 Open 385 Closed
1,062 Open 385 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

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
1
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 release-blocker Blocks the next release from happening spec-bug Something which is in the spec, but is wrong
#1964 opened Oct 7, 2024 by turt2live
1
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
Stop using canonifyURLs
#1957 opened Sep 30, 2024 by Johennes
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
Add 403 response error to /_matrix/federation/v1/state_ids/{roomId} improvement An idea/future MSC for the spec
#1912 opened Jul 19, 2024 by anoadragon453
1
Should we be descriptive or prescriptive about how room upgrades work?
#1906 opened Jul 8, 2024 by turt2live
Servers don't enforce PDU format
#1904 opened Jul 7, 2024 by Kladki
2
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
2
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
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
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
ProTip! Follow long discussions with comments:>50.