Skip to content

MSC4468: Reporting to communities (via to-device)#4468

Draft
turt2live wants to merge 3 commits into
mainfrom
travis/msc/reporting-v2/x-report-to-community
Draft

MSC4468: Reporting to communities (via to-device)#4468
turt2live wants to merge 3 commits into
mainfrom
travis/msc/reporting-v2/x-report-to-community

Conversation

@turt2live

@turt2live turt2live commented May 12, 2026

Copy link
Copy Markdown
Member

Rendered

Note: This is a draft while it undergoes very early review. The idea needs validation prior to any implementation begins.

Alternatives:

@turt2live turt2live changed the title MSC: Reporting to communities MSC4468: Reporting to communities May 12, 2026
@turt2live turt2live added 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. A-Safety A-Reporting v2 proposal A matrix spec change proposal. Process state. labels May 12, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Implementation requirements:

  • Withheld pending review.

@turt2live turt2live changed the title MSC4468: Reporting to communities MSC4468: Reporting to communities (via to-device) May 13, 2026
@turt2live turt2live added the A-Client Server Client-Server API label May 13, 2026
@tulir tulir mentioned this pull request May 13, 2026
pull Bot pushed a commit to elsiehupp/element-web that referenced this pull request May 14, 2026
* Remove MSC3215 (Report to Moderators) labs feature

T&S does not believe this is used, and intends to replace it during Reporting v2 anyway.

Original MSC: matrix-org/matrix-spec-proposals#3215

New (WIP) MSC: matrix-org/matrix-spec-proposals#4468

(This PR/commit doesn't add MSC4468 support because it's unclear if we should use MSC4468 directly or via another endpoint like MSC4457)

[MSC4457]: matrix-org/matrix-spec-proposals#4457

* Remove unused state: isRoomEncrypted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Client Server Client-Server API A-Reporting v2 A-Safety 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. Process state.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant