-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
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
Authorization rules are confusing
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#1642
opened Sep 21, 2023 by
turt2live
join_authorised_via_users_server
user must be joined to the room
A-Room-spec
#1477
opened Mar 29, 2023 by
turt2live
Clarify what unstable and stable mean as words with respect to room versions
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#891
opened Sep 2, 2021 by
turt2live
auth rules refer to 'required power level' but do not define it
A-Room-spec
Something to do with the room version specifications
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
help wanted
Interested in contributing to the spec? These would be great additions!
#710
opened Oct 30, 2020 by
richvdh
Clarify sha1 representation in state resolution sort
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#706
opened Oct 20, 2020 by
achan1989
English: If sender's domain doesn't matches state_key, reject.
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#658
opened Jul 1, 2020 by
turt2live
let's upgrade all public rooms from v1 and spec that all v1 rooms should be frozen henceforth
A-Client-Server
Issues affecting the CS API
A-Room-spec
Something to do with the room version specifications
feature
Suggestion for a significant extension which needs considerable consideration
#624
opened May 21, 2020 by
ara4n
The v2 room spec incorrectly seems to imply that you have to transitively walk the DAG for state res to work
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#619
opened May 12, 2020 by
ara4n
Event ID format not specified for room v1/v2
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#551
opened Oct 15, 2019 by
joepie91
it's a bit confusing that https://matrix.org/docs/spec/rooms/v4 duplicates all the baggage from v3, rather than just being a short description of the change
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#518
opened Aug 3, 2019 by
ara4n
https://matrix.org/docs/spec/rooms/v2 should link back to the v2 rooms MSC or something for people wanting more detail and context
A-Room-spec
Something to do with the room version specifications
clarification
An area where the expected behaviour is understood, but the spec could do with being more explicit
#517
opened Aug 3, 2019 by
ara4n
ProTip!
no:milestone will show everything without a milestone.