X Tutup
Skip to content

MSC4284: Policy Servers#4284

Merged
turt2live merged 33 commits intomainfrom
travis/msc/placeholder/00-apr072025
Feb 22, 2026
Merged

MSC4284: Policy Servers#4284
turt2live merged 33 commits intomainfrom
travis/msc/placeholder/00-apr072025

Conversation

@turt2live
Copy link
Member

@turt2live turt2live commented Apr 7, 2025

Rendered

Disclosure: I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published as a Trust & Safety team member allocated in full to the Foundation.


SCT Stuff:

MSC Checklist

FCP tickyboxes

@turt2live turt2live added proposal A matrix spec change proposal 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. safety labels Apr 7, 2025
@turt2live turt2live changed the title [WIP] MSC4284: Placeholder [WIP] MSC4284: Policy Servers Apr 16, 2025
@turt2live turt2live added s2s Server-to-Server API (federation) client-server Client-Server API proposal A matrix spec change proposal and removed proposal A matrix spec change proposal labels Apr 16, 2025
@mimi89999

This comment was marked as duplicate.

@vindicatorr

This comment was marked as duplicate.

with more detail, like in [MSC4387: `M_SAFETY` error code](https://github.com/matrix-org/matrix-spec-proposals/pull/4387).

**Note**: Policy servers MAY return *any* of the above errors to indicate failure. For example, if a
policy server wishes to hide whether it knows about a room, it MAY return `400 M_FORBIDDEN` instead
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was there some particular reason for picking 400 over 403? 400 M_FORBIDDEN feels weird

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No significant thought was put behind the example. A policy server could return 403 M_FORBIDDEN instead if it wants to.


```json5
{
"via": "policy.example.org", // the server name providing room policy (the "policy server")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm neutral on all these suggestions.

@mscbot
Copy link
Collaborator

mscbot commented Feb 17, 2026

🔔 This is now entering its final comment period, as per the review above. 🔔

@mscbot mscbot added final-comment-period This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days. and removed proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. labels Feb 17, 2026
@turt2live turt2live removed the 00-weekly-pings Tracking for weekly pings in the SCT office. 00 to make it first in the labels list. label Feb 17, 2026
@turt2live turt2live moved this from Ready for FCP ticks to In FCP in Spec Core Team Workflow Feb 17, 2026
@mscbot
Copy link
Collaborator

mscbot commented Feb 22, 2026

The final comment period, with a disposition to merge, as per the review above, is now complete.

@mscbot mscbot added finished-final-comment-period and removed disposition-merge final-comment-period This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days. labels Feb 22, 2026
@turt2live turt2live merged commit 9482230 into main Feb 22, 2026
1 check passed
@turt2live turt2live deleted the travis/msc/placeholder/00-apr072025 branch February 22, 2026 18:59
@turt2live turt2live added spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec and removed finished-final-comment-period labels Feb 22, 2026
@turt2live turt2live moved this from In FCP to Requires spec writing in Spec Core Team Workflow Feb 22, 2026
@turt2live turt2live self-assigned this Feb 22, 2026
@turt2live
Copy link
Member Author

Spec PR: matrix-org/matrix-spec#2332

@turt2live turt2live added spec-pr-in-review A proposal which has been PR'd against the spec and is in review and removed spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec labels Mar 9, 2026
@turt2live turt2live moved this from Requires spec writing to Requires spec PR review in Spec Core Team Workflow Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client-server Client-Server API kind:core MSC which is critical to the protocol's success proposal A matrix spec change proposal s2s Server-to-Server API (federation) safety spec-pr-in-review A proposal which has been PR'd against the spec and is in review

Projects

Status: Requires spec PR review

Development

Successfully merging this pull request may close these issues.

X Tutup