Rework the "report" button so that it reaches the right person

[Yoric]

Right now, the "report" button reports to the user's homeserver admin. That's often the wrong person.

I can think of two kinds of abuse reports:

1. This user is a spambot/a troll/... and has nothing to do on this channel (most common reports). => Should be routed to the channel moderators. The moderator may decide to report this to the homeserver admin, their call.
2. This channel is violating the server's terms (or perhaps it is being used for illegal stuff). => Should be routed to the homeserver admin.

At the moment, since we route everything to the homeserver admin, this means that:

• the homeserver admin is swamped by reports they cannot act upon immediately;
• if the channel is encrypted, and unless they are already channel members, they have no information to act;
• even if the channel is unencrypted, they typically don't know the rules of a channel, or its members, etc.

So, we need two report buttons, along the lines of:

1. "Report behavior to the channel moderators." (sends a link to the offending line as PM to all channel moderators)
2. "Report the entire channel to the admin of {your_homeserver}." (does what it does at the moment)

If the user actually is the moderator, 1. could change to "Report behavior to the admin of {your_homeserver}."

[t3chguy]

This likely belongs in Synapse or the spec. As the spec just says

Reports an event as inappropriate to the server, which may then notify the appropriate people.

https://matrix.org/docs/spec/client_server/r0.6.1#post-matrix-client-r0-rooms-roomid-report-eventid

so likely needs some more configurability and guidance.

[Yoric]

This likely belongs in Synapse or the spec. As the spec just says

Reports an event as inappropriate to the server, which may then notify the appropriate people.

https://matrix.org/docs/spec/client_server/r0.6.1#post-matrix-client-r0-rooms-roomid-report-eventid

so likely needs some more configurability and guidance.

Do you think so?

We still connect one of the buttons to /_matrix/client/r0/rooms/{roomId}/report/{eventId}. This doesn't need to change spec.

And the other button sends a PM, which doesn't feel like a spec change.

[turt2live]

T&S is experimenting with routing in Reporting v2. Though the MSC itself doesn't describe routing, the carve out for it is in matrix-org/matrix-spec-proposals#4457

Closing in favour of spec work in the area.