Skip to content

MSC3955: Extensible Events - Automated event mixin (notices)#3955

Open
turt2live wants to merge 2 commits into
mainfrom
travis/msc/extev/notices
Open

MSC3955: Extensible Events - Automated event mixin (notices)#3955
turt2live wants to merge 2 commits into
mainfrom
travis/msc/extev/notices

Conversation

@turt2live
Copy link
Copy Markdown
Member

@turt2live turt2live marked this pull request as ready for review January 13, 2023 04:54
@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. labels Jan 13, 2023
Comment thread proposals/3955-extensible-events-bot-notice-mixin.md Outdated
Comment thread proposals/3955-extensible-events-bot-notice-mixin.md
Comment on lines +33 to +34
When an event is flagged as automated, the client should render that event differently compared to
normal. For example, reducing the opacity of the event.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What about (default?) push rules? m.notice events today are silent by default via .m.rule.suppress_notices.

@turt2live turt2live moved this from Backlog to Next in Extensible Events May 4, 2026
@turt2live turt2live self-assigned this May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

Status: Next
Status: Tracking for review
Status: Scheduled - v1.10

Development

Successfully merging this pull request may close these issues.

4 participants