-
Notifications
You must be signed in to change notification settings - Fork 401
Pull requests: matrix-org/matrix-spec-proposals
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
MSC4313: Require HTML 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
<ol>
start
Attribute support
client-server
#4313
opened Jul 15, 2025 by
HarHarLinks
Loading…
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…
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…
MSC4310: MatrixRTC decline 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
m.rtc.notification
client-server
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
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
MSC4307: Validate that This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days.
kind:core
MSC which is critical to the protocol's success
proposal
A matrix spec change proposal
room-spec
Something to do with the room version specifications
auth_events
are in the correct room
disposition-merge
final-comment-period
#4307
opened Jul 8, 2025 by
richvdh
Loading…
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
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…
[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.
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…
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…
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…
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…
[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
[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.
[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.
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
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…
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…
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…
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…
MSC4291: Room IDs as hashes of the create event
disposition-merge
final-comment-period
This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days.
kind:core
MSC which is critical to the protocol's success
maybe v12?
candidate for room version 12
proposal
A matrix spec change proposal
requires-room-version
An idea which will require a bump in room version
room-spec
Something to do with the room version specifications
s2s
Server-to-Server API (federation)
unassigned-room-version
Remove this label when things get versioned.
#4291
opened May 20, 2025 by
ara4n
Loading…
[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.
[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.
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.