matrix-spec/content/client-server-api/modules/report_content.md


### Reporting Content

Users may encounter content which they find inappropriate and should be
able to report it to the server administrators or room moderators for
review. This module defines a way for users to report content.

#### Client behaviour

{{% http-api spec="client-server" api="report_content" %}}

#### Server behaviour

Servers are free to handle the reported content however they desire.
This may be a dedicated room to alert server administrators to the
reported content or some other mechanism for notifying the appropriate
people.

Particularly during waves of harmful content, users may report whole
rooms instead of individual events. Server administrators and safety teams
should, therefore, be cautious not to shut down rooms that might otherwise
be legitimate.

{{% changed-in v="1.8" %}} When processing event reports, servers MUST
verify that the reporting user is currently joined to the room the event
is in before accepting a report.

{{% added-in v="1.12" %}} Contrarily, servers MUST NOT restrict room reports
based on whether or not the reporting user is joined to the room. This is
because users can be exposed to harmful content without being joined to a
room. For instance, through room directories or invites.
Add support for modules 4 years ago
			`### Reporting Content`

			`Users may encounter content which they find inappropriate and should be`
			`able to report it to the server administrators or room moderators for`
			`review. This module defines a way for users to report content.`

			`#### Client behaviour`

Update content to call the new template for HTTP APIs 4 years ago			`{{% http-api spec="client-server" api="report_content" %}}`
Add support for modules 4 years ago
			`#### Server behaviour`

			`Servers are free to handle the reported content however they desire.`
			`This may be a dedicated room to alert server administrators to the`
			`reported content or some other mechanism for notifying the appropriate`
			`people.`
Add spec for MSC2449: Require users to have visibility on an event when submitting reports (#1517) * Add MSC2249 support * changelog * Add a line on verification * Changes based on review feedback * Apply suggestions from code review Co-authored-by: Travis Ralston <travpc@gmail.com> * move tags field to the bottom of report_content.yaml * fix duplicated content now how did that happen * fix up the 404 response schema it wasn't displaying correctly in the rendered spec otherwise * remove erroneous schema reference * 1.7 -> 1.8 Co-authored-by: Travis Ralston <travpc@gmail.com> --------- Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> Co-authored-by: Travis Ralston <travpc@gmail.com> Co-authored-by: Andrew Morgan <andrew@amorgan.xyz> 1 year ago
MSC4151: Reporting rooms (#1938) 1 month ago			`Particularly during waves of harmful content, users may report whole`
			`rooms instead of individual events. Server administrators and safety teams`
			`should, therefore, be cautious not to shut down rooms that might otherwise`
			`be legitimate.`

Always use `%` delimiter for `added-in` and `changed-in` shortcodes (#1975) The `<>` delimiters are not necessary for the shortcode to be rendered inline, and in some cases they break some expectations: a shortcode that is separated from other text to be in its own paragraph is not actually wrapped by a `p` element, breaking the spacing between paragraphs. Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr> 3 weeks ago			`{{% changed-in v="1.8" %}} When processing event reports, servers MUST`
MSC4151: Reporting rooms (#1938) 1 month ago			`verify that the reporting user is currently joined to the room the event`
			`is in before accepting a report.`

Always use `%` delimiter for `added-in` and `changed-in` shortcodes (#1975) The `<>` delimiters are not necessary for the shortcode to be rendered inline, and in some cases they break some expectations: a shortcode that is separated from other text to be in its own paragraph is not actually wrapped by a `p` element, breaking the spacing between paragraphs. Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr> 3 weeks ago			`{{% added-in v="1.12" %}} Contrarily, servers MUST NOT restrict room reports`
MSC4151: Reporting rooms (#1938) 1 month ago			`based on whether or not the reporting user is joined to the room. This is`
			`because users can be exposed to harmful content without being joined to a`
			`room. For instance, through room directories or invites.`