Skip to content

Issues: matrix-org/matrix-spec-proposals

Do not open issues here
#3962 opened Jan 30, 2023 by turt2live
Open
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

Clear current search query, filters, and sorts
520 Open 407 Closed
520 Open 407 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

MSC4266: Policies in /.well-known/matrix/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
#4266 opened Feb 14, 2025 by Johennes Loading…
2
MSC4265: Data Protection Officer contact in /.well-known/matrix/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
#4265 opened Feb 14, 2025 by Johennes Loading…
2
MSC4264: Tokens for Contacting Accounts or Joining Semi-Public Rooms 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 requires-room-version An idea which will require a bump in room version unassigned-room-version Remove this label when things get versioned.
#4264 opened Feb 11, 2025 by thomasfiala Loading…
4 tasks done
14
MSC4263: Preventing MXID enumeration via key queries 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
#4263 opened Feb 4, 2025 by Johennes Loading…
4
MSC4262: Sliding Sync Extension: Profile Updates 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
#4262 opened Feb 3, 2025 by tcpipuk Loading…
1
MSC4261: "Do not encrypt for device" flag 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
#4261 opened Feb 1, 2025 by uhoreg Loading…
2
MSC4260: Reporting users (Client-Server API) 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.
#4260 opened Jan 30, 2025 by turt2live Loading…
12
MSC4259: Profile Update EDUs for Federation 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 s2s Server-to-Server API (federation)
#4259 opened Jan 30, 2025 by tcpipuk Loading…
7
MSC4258: Federated User Directory 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 s2s Server-to-Server API (federation)
#4258 opened Jan 29, 2025 by MatMaul Loading…
12
MSC4257: Profiles Arent Auth: Move profile contents to a separate event 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 s2s Server-to-Server API (federation) unassigned-room-version Remove this label when things get versioned.
#4257 opened Jan 27, 2025 by TheArcaneBrony • Draft
2
MSC4256: RFC 9420 MLS mode Matrix client-server Client-Server API e2e implementation-needs-checking The MSC has an implementation, but the SCT has not yet checked it. kind:core MSC which is critical to the protocol's success proposal A matrix spec change proposal
#4256 opened Jan 24, 2025 by dklimpel Loading…
81
MSC4255: Bulk Profile Updates 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
#4255 opened Jan 23, 2025 by tcpipuk Loading…
14
MSC4254: Usage of RFC7009 Token Revocation for Matrix client logout client-server Client-Server API disposition-merge kind:core MSC which is critical to the protocol's success matrix-2.0 Required for Matrix 2.0 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.
#4254 opened Jan 17, 2025 by sandhose Loading…
12
MSC4253: Modifying or rejecting accepted MSCs kind:core MSC which is critical to the protocol's success process Related to the spec process itself (MSC process) proposal A matrix spec change proposal
#4253 opened Jan 15, 2025 by turt2live Loading…
17
MSC4252: Extensible Events modification: State event handling 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
#4252 opened Jan 15, 2025 by turt2live Loading…
2
MSC4250: Authenticated media v2 (Cookie authentication for Client-Server API) 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
#4250 opened Jan 11, 2025 by turt2live Loading…
1
10
MSC4249: Removal of legacy media endpoints client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec proposal A matrix spec change proposal
#4249 opened Jan 2, 2025 by turt2live Loading…
1
MSC4248: Pull-based presence 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
#4248 opened Dec 27, 2024 by nexy7574 • Draft
8
MSC4247: User Pronouns 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
#4247 opened Dec 27, 2024 by everypizza1 Loading…
35
MSC4246: Sending to-device messages as/to a server 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
#4246 opened Dec 21, 2024 by turt2live Loading…
1
MSC4245: Immutable encryption algorithm client-server Client-Server API e2e 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
#4245 opened Dec 21, 2024 by turt2live Loading…
9
[WIP] MSC4244: RFC 9420 MLS for Matrix client-server Client-Server API e2e 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
#4244 opened Dec 21, 2024 by turt2live • Draft
6
[WIP] Placeholder stub 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
#4243 opened Dec 17, 2024 by kegsay • Draft
[WIP] Placeholder stub 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
#4242 opened Dec 17, 2024 by kegsay • Draft
MSC4238: Pinned events read marker 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
#4238 opened Dec 10, 2024 by ajbura Loading…
5
ProTip! Find all open issues with in progress development work with linked:pr.