Skip to content

Pull requests: matrix-org/matrix-spec-proposals

New pull request New
521 Open 1,754 Closed
521 Open 1,754 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
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

MatrixRTC proposal | Update to-device key event format + cleaning
#4318 opened Jul 30, 2025 by BillCarsonFr • Draft
MSC4317: Signed profile data client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4317 opened Jul 29, 2025 by Johennes Loading…
7
MSC4316: External cross-signing signatures with X.509 certificates and (semi-)automated verification client-server Client-Server API e2e kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4316 opened Jul 29, 2025 by Johennes Loading…
1
MSC4313: Require HTML <ol> start Attribute support client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4313 opened Jul 15, 2025 by HarHarLinks Loading…
15
MSC4312: Resetting cross-signing keys in the OAuth world client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4312 opened Jul 15, 2025 by Johennes Loading…
2
MSC4311: Ensuring the create event is available on invites and knocks client-server Client-Server API kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal s2s Server-to-Server API (federation)
#4311 opened Jul 11, 2025 by turt2live Loading…
15
MSC4310: MatrixRTC decline m.rtc.notification client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4310 opened Jul 10, 2025 by toger5 • Draft
5 tasks
MSC4309: Finalised delayed event on sync client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4309 opened Jul 10, 2025 by toger5 • Draft
5 tasks
MSC4308: Thread Subscriptions extension to Sliding Sync client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4308 opened Jul 9, 2025 by reivilibre • Draft
2
MSC4306: Thread Subscriptions client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4306 opened Jul 8, 2025 by reivilibre • Draft
48
MSC4305: Pushed Authorization Requests (PARs) for OAuth authentication client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4305 opened Jul 4, 2025 by Johennes Loading…
2
[WIP] MSC4304: Placeholder action-required Just a bright label to differentiate arbitrary proposals. needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal-placeholder This label is removed and replaced with `proposal` once the placeholder status is cleared.
#4304 opened Jul 3, 2025 by turt2live • Draft
MSC4303: Disallowing non-compliant user IDs in rooms kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal requires-room-version An idea which will require a bump in room version unassigned-room-version Remove this label when things get versioned.
#4303 opened Jun 27, 2025 by tulir Loading…
3
MSC4302: Exchanging FHIR resources via Matrix events client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4302 opened Jun 20, 2025 by Johennes Loading…
6
MSC4301: Event capability negotiation between clients client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4301 opened Jun 16, 2025 by Johennes Loading…
6
MSC4300: Processing status requests & responses client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4300 opened Jun 16, 2025 by Johennes Loading…
7
[WIP] MSC4299: trusted users client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4299 opened Jun 12, 2025 by nexy7574 • Draft
18
[WIP] MSC4298: Room version components for 'Redact on ban' client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal requires-room-version An idea which will require a bump in room version safety unassigned-room-version Remove this label when things get versioned.
#4298 opened Jun 10, 2025 by turt2live • Draft
[WIP] Placeholder action-required Just a bright label to differentiate arbitrary proposals. needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal-placeholder This label is removed and replaced with `proposal` once the placeholder status is cleared.
#4297 opened Jun 6, 2025 by kegsay • Draft
1
MSC4296: Mentions for device IDs client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal push
#4296 opened Jun 4, 2025 by Johennes • Draft
12
MSC4295: Bot bounce limit - a better loop prevention mechanism client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
#4295 opened May 31, 2025 by m13253 Loading…
12
MSC4294: Ignore and mass ignore invites client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal safety
#4294 opened May 29, 2025 by grinapo Loading…
6
MSC4293: Redact on ban client-server Client-Server API disposition-merge kind:core MSC which is critical to the protocol's success proposal A matrix spec change proposal proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. safety unresolved-concerns This proposal has at least one outstanding concern
#4293 opened May 27, 2025 by turt2live Loading…
52
MSC4292: Handling incompatible room versions in clients client-server Client-Server API kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal safety
#4292 opened May 26, 2025 by turt2live Loading…
8
[WIP] Placeholder action-required Just a bright label to differentiate arbitrary proposals. needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal-placeholder This label is removed and replaced with `proposal` once the placeholder status is cleared.
#4290 opened May 20, 2025 by ara4n • Draft
1
ProTip! Filter pull requests by the default branch with base:main.