MSC4277: Harmonizing the reporting endpoints by Johennes · Pull Request #4277 · matrix-org/matrix-spec-proposals

Johennes · 2025-03-21T10:01:09Z

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.

SCT Stuff:

MSC checklist

FCP tickyboxes

Signed-off-by: Johannes Marbach <[email protected]>

turt2live · 2025-03-21T18:41:49Z

proposals/4277-reporting-harmonization.md

Implementation requirements:

Server

200 regardless of event / room existence: element-hq/synapse#18263

I'm unsure if the random delay / constant time part requires an implementation. The spec already mentions this for the event reporting endpoint but Synapse doesn't appear to implement it and it's not part of element-hq/synapse#18120 either.

I've added the removal of score into element-hq/synapse#18263. Synapse didn't do anything else than assert the type anyway.

Implemented in continuwuity #919.

proposals/4277-reporting-harmonization.md

Half-Shot · 2025-03-27T10:11:18Z

proposals/4277-reporting-harmonization.md

+
+## Potential issues
+
+The `reason` field on the room and user reporting endpoints is currently


Honestly, I find it bizarre that reason is required but may be empty string. I suppose this might not be the MSC to change it, but I'd rather we just made it optional.

I think I understand the value of requiring it to be filled for spam protection. The combination of required but allowed to be empty strikes me as slightly odd, too, but it's hard to judge without knowing T&S's future plans for the field.

Generally though, I suppose if we later go from required but possibly empty to required and not empty, it'll be just as much a breaking change for clients as if we went from optional to required and not empty.

It's hard to say. Even if the field was required people could just keyboard smash the field. I'm not really going to die on this hill though, I just think we should unify it in one direction.

My feeling for T&S that any report is a useful report, and that tooling is smart enough these days that we can make use of the room_id / event_id to do preliminary investigations even if the reason context isn't useful.

proposals/4277-reporting-harmonization.md

…ints (#18263) [MSC4277](matrix-org/matrix-spec-proposals#4277): Harmonizing the reporting endpoints

turt2live · 2025-08-06T16:31:39Z

This MSC has been put forward as potentially ready for FCP. T&S is aware of some features which may need mirroring to the trio of endpoints, and may want to include them in this MSC (the MSC hasn't been reviewed to see if they're already addressed).

Next steps are for T&S to review the MSC, then send it for SCT review. Feel free to ping me on either if the process takes too long.

@clokep

Tested on NetBSD 9 amd64 (federation, multiple clients) # Synapse 1.135.0 (2025-08-01) ## Features - Add `recaptcha_private_key_path` and `recaptcha_public_key_path` config option. ([\#17984](element-hq/synapse#17984), [\#18684](element-hq/synapse#18684)) - Add plain-text handling for rich-text topics as per [MSC3765](matrix-org/matrix-spec-proposals#3765). ([\#18195](element-hq/synapse#18195)) - If enabled by the user, server admins will see [soft failed](https://spec.matrix.org/v1.13/server-server-api/#soft-failure) events over the Client-Server API. ([\#18238](element-hq/synapse#18238)) - Add experimental support for [MSC4277: Harmonizing the reporting endpoints](matrix-org/matrix-spec-proposals#4277). ([\#18263](element-hq/synapse#18263)) - Add ability to limit amount of media uploaded by a user in a given time period. ([\#18527](element-hq/synapse#18527)) - Enable workers to write directly to the device lists stream and handle device list updates, reducing load on the main process. ([\#18581](element-hq/synapse#18581)) - Support arbitrary profile fields. Contributed by @clokep. ([\#18635](element-hq/synapse#18635)) - Advertise support for Matrix v1.12. ([\#18647](element-hq/synapse#18647)) - Add an option to issue redactions as an admin user via the [admin redaction endpoint](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#redact-all-the-events-of-a-user). ([\#18671](element-hq/synapse#18671)) - Add experimental and incomplete support for [MSC4306: Thread Subscriptions](https://github.com/matrix-org/matrix-spec-proposals/blob/rei/msc_thread_subscriptions/proposals/4306-thread-subscriptions.md). ([\#18674](element-hq/synapse#18674)) - Include `event_id` when getting state with `?format=event`. Contributed by @tulir @ Beeper. ([\#18675](element-hq/synapse#18675))

proposals/4277-reporting-harmonization.md

Co-authored-by: David Baker <[email protected]>

… landed Signed-off-by: Johannes Marbach <[email protected]>

proposals/4277-reporting-harmonization.md

Co-authored-by: Hubert Chathi <[email protected]>

richvdh · 2026-02-03T14:50:52Z

proposals/4277-reporting-harmonization.md

+Matrix currently has three reporting endpoints:
+
+- [`/_matrix/client/v3/rooms/{roomId}/report/{eventId}`] ([added] in Matrix
+  0.4.0, no MSC known)


it was MSC739, fwiw. That's what MSCs used to look like, back in the day.

mscbot · 2026-02-03T15:11:56Z

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

mscbot · 2026-02-08T15:12:06Z

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

Johennes · 2026-02-12T13:09:56Z

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

turt2live · 2026-03-03T16:48:07Z

Merged 🎉

Johennes changed the title ~~MSCXXXX: Harmonizing the reporting endpoints~~ MSC4277: Harmonizing the reporting endpoints Mar 21, 2025

MSC4277: Harmonizing the reporting endpoints

0f9c41e

Signed-off-by: Johannes Marbach <[email protected]>

Johennes force-pushed the johannes/reporting-harmonization branch from 42df948 to 0f9c41e Compare March 21, 2025 10:03

Johennes added 5 commits March 21, 2025 11:03

Fix typo

c12e1e9

Add missing extension

34309cb

One more typo

0258d25

Another typo

8f9de37

Add missing period

eca1255

Johennes marked this pull request as ready for review March 21, 2025 10:08

Johennes mentioned this pull request Mar 21, 2025

MSC4260: Reporting users (Client-Server API) matrix-org/matrix-spec#2093

Merged

3 tasks

turt2live added 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 21, 2025

turt2live reviewed Mar 21, 2025

View reviewed changes

turt2live requested changes Mar 21, 2025

View reviewed changes

proposals/4277-reporting-harmonization.md Outdated Show resolved Hide resolved

Exclude harmonising the reason parameter

67c94b7

Johennes requested a review from turt2live March 24, 2025 07:07

Half-Shot reviewed Mar 27, 2025

View reviewed changes

Remove leftover potential issue

efa3f23

Half-Shot reviewed Mar 27, 2025

View reviewed changes

proposals/4277-reporting-harmonization.md Show resolved Hide resolved

Add removal of score property

b3ac83f

MadLittleMods mentioned this pull request Jun 27, 2025

Add experimental support for MSC4277 element-hq/synapse#18263

Merged

3 tasks

MadLittleMods pushed a commit to element-hq/synapse that referenced this pull request Jul 9, 2025

Add experimental support for MSC4277: Harmonizing the reporting endpo…

e1b429d

…ints (#18263) [MSC4277](matrix-org/matrix-spec-proposals#4277): Harmonizing the reporting endpoints

turt2live added this to Spec Core Team Workflow Aug 5, 2025

github-project-automation bot moved this to Tracking for review in Spec Core Team Workflow Aug 5, 2025

turt2live moved this from Tracking for review to Proposed for FCP readiness in Spec Core Team Workflow Aug 5, 2025

turt2live self-assigned this Aug 6, 2025

dbkr reviewed Jan 13, 2026

View reviewed changes

proposals/4277-reporting-harmonization.md Outdated Show resolved Hide resolved

Johennes and others added 2 commits January 14, 2026 08:14

Fix typo

2c3e030

Co-authored-by: David Baker <[email protected]>

Link to the spec for the user reporting endpoint now that MSC4260 has…

2b8172f

… landed Signed-off-by: Johannes Marbach <[email protected]>

uhoreg reviewed Jan 21, 2026

View reviewed changes

proposals/4277-reporting-harmonization.md Outdated Show resolved Hide resolved

proposals/4277-reporting-harmonization.md Outdated Show resolved Hide resolved

Johennes and others added 2 commits January 21, 2026 06:32

Update proposals/4277-reporting-harmonization.md

5c14bcf

Co-authored-by: Hubert Chathi <[email protected]>

Update proposals/4277-reporting-harmonization.md

a4123f4

Co-authored-by: Hubert Chathi <[email protected]>

richvdh reviewed Feb 3, 2026

View reviewed changes

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 3, 2026

turt2live moved this from Ready for FCP ticks to In FCP in Spec Core Team Workflow Feb 3, 2026

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 3, 2026

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 8, 2026

turt2live merged commit ced0a90 into matrix-org:main Feb 8, 2026
1 check passed

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 8, 2026

turt2live moved this from In FCP to Requires spec writing in Spec Core Team Workflow Feb 8, 2026

tulir 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 Feb 12, 2026

turt2live moved this from Requires spec writing to Requires spec PR review in Spec Core Team Workflow Feb 12, 2026

turt2live added merged A proposal whose PR has merged into the spec! and removed spec-pr-in-review A proposal which has been PR'd against the spec and is in review labels Mar 3, 2026

turt2live moved this from Requires spec PR review to Merged/Done in Spec Core Team Workflow Mar 3, 2026

This was referenced Mar 3, 2026

Implement Matrix 1.18 changes ruma/ruma#2345

Open

client-api: Remove the score field from the report_content endpoint ruma/ruma#2403

Merged


		## Potential issues

		The `reason` field on the room and user reporting endpoints is currently

Conversation

Johennes commented Mar 21, 2025 • edited by turt2live Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

turt2live commented Aug 6, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mscbot commented Feb 3, 2026

Uh oh!

mscbot commented Feb 8, 2026

Uh oh!

Uh oh!

Johennes commented Feb 12, 2026

Uh oh!

turt2live commented Mar 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants

Johennes commented Mar 21, 2025 •

edited by turt2live

Loading