Skip to content
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.

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

MSC4271: Recommended enabled-ness for default push rules #4271

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Johennes
Copy link
Contributor

@Johennes Johennes commented Mar 3, 2025

Rendered

Relates to: element-hq/synapse#9325


In line with matrix-org/matrix-spec#1700, the following disclosure applies:

I am a Systems Architect at gematik, Software Engineer at Filament and Unomed, Matrix community member and former Element employee. This proposal was written and published with my gematik hat on.

@Johennes Johennes changed the title MSCXXXX: Recommended enabled-ness for default push rules MSC4271: Recommended enabled-ness for default push rules Mar 3, 2025
@Johennes Johennes force-pushed the johannes/recommended-enabled-ness-for-default-push-rules branch from 58606d1 to c07f899 Compare March 3, 2025 12:39
@Johennes Johennes marked this pull request as ready for review March 3, 2025 12:42
@turt2live turt2live added push proposal A matrix spec change proposal 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. labels Mar 3, 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

Comment on lines +11 to +13
customisation for more specialised usage scenarios. As an example, a server may
want to disable `.m.rule.suppress_notices` by default because it uses server
notices for time critical or otherwise important notifications.
Copy link
Member

Choose a reason for hiding this comment

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

Is using notices the proper thing to do here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You mean the admin should just use a normal room instead?

I was thinking that server notices may be FYIs of low relevance but they could also be of equal importance to regular messages depending on how the admin uses them.

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: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 push
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants