Skip to content

Conversation

@velikopter
Copy link

@velikopter velikopter commented Oct 22, 2025

@velikopter velikopter changed the title MSCXXXX: Server opt-out of specific EDU types MSC4373: Server opt-out of specific EDU types Oct 22, 2025
@turt2live turt2live added proposal A matrix spec change proposal s2s Server-to-Server API (federation) 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. labels Oct 22, 2025
Copy link
Member

Choose a reason for hiding this comment

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

Implementation requirements:

  • Server (setting value)
  • Server (reading value)

Copy link
Author

Choose a reason for hiding this comment

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

Comment on lines 37 to 39
If the EDU type is set to `true` or absent, the EDU SHOULD be sent to the target
homeserver, unless other factors disallow it (such as room ACLs, where that is
relevant).
Copy link
Contributor

Choose a reason for hiding this comment

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

If the receiving server can decide what to receive, could the sending server also have an interest to decide what to send? E.g. a server might want to opt out of sending presence for its users over federation. I wonder if this would warrant a MAY rather than a SHOULD?

Copy link
Contributor

Choose a reason for hiding this comment

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

A MAY would also make the new endpoint sort of equivalent to the /capabilities endpoint in the CS API.

Copy link
Author

Choose a reason for hiding this comment

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

It does, I'll change it to a MAY

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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 s2s Server-to-Server API (federation)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants