-
Notifications
You must be signed in to change notification settings - Fork 385
Issues: matrix-org/matrix-spec-proposals
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
[oops, i filed this wrongly here] Add some sort of approval step before a new user can send images
#4212
by ell1e
was closed Oct 6, 2024
Documentation unclear about requirements / build.sh no good perceptible warnings / errors
spec-bug
Something which is in the spec, but is wrong
#3747
by raypatterson77
was closed Feb 28, 2022
v1.2 changelog does not merge entries with identical text
aesthetic
A suggestion or issue relating to the representation of the spec
#3742
by richvdh
was closed Feb 23, 2022
MSC 1929 admin contact: new roles in addition to admin and security: abuse and support
#3740
by bkil
was closed Feb 22, 2022
Auth rules for knocking are wrong
spec-bug
Something which is in the spec, but is wrong
#3736
by timokoesters
was closed Feb 22, 2022
Mentions of Something which is in the spec, but is wrong
m.login.token
linger in the spec
spec-bug
#3733
by ShadowJonathan
was closed Feb 18, 2022
wire
clarification
An area where the spec could do with being more explicit
#3717
by D5n9sMatrix
was closed Feb 9, 2022
v1.2 Appservice login type identifier inconsistency
spec-bug
Something which is in the spec, but is wrong
#3709
by Schuwi
was closed Feb 14, 2022
the thing tagged An area where the spec could do with being more explicit
v1.2
is not v1.2
clarification
#3704
by richvdh
was closed Feb 3, 2022
spec for An area where the spec could do with being more explicit
/send_join
response is contradictory
clarification
#3702
by richvdh
was closed Feb 7, 2022
Event with invalid auth_events
clarification
An area where the spec could do with being more explicit
#3695
by timokoesters
was closed Feb 10, 2022
Inconsistency for successive references in schemas and parsing
#3689
by afranke
was closed Feb 2, 2022
"Unchanged since last version" sections of room version specs is in seemingly random order
aesthetic
A suggestion or issue relating to the representation of the spec
room-spec
Something to do with the room version specifications
#3656
by turt2live
was closed Jan 31, 2022
Missing knock rule on v7 room
release-blocker
spec-bug
Something which is in the spec, but is wrong
#3648
by gnieto
was closed Jan 20, 2022
Should room name be limited to 255 bytes?
clarification
An area where the spec could do with being more explicit
#3641
by aaronraimist
was closed Feb 22, 2022
Push rules - Don't search domains for keywords
improvement
A suggestion for a relatively simple improvement to the protocol
push
#3640
by JokerGermany
was closed Jan 13, 2022
Event::depth
does not specify if negative values are (dis)allowed
clarification
#3629
by ShadowJonathan
was closed Jan 7, 2022
Paths in OpenAPI JSON file are missing
/_matrix/client/vX
prefix
#3625
by aaronraimist
was closed Jan 19, 2022
Example response for Something which is in the spec, but is wrong
GET /_matrix/federation/v1/user/devices/{userId}
omits missing field
spec-bug
#3620
by DMRobertson
was closed Jan 4, 2022
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.