MSC4202: Reporting User Profiles

[tcpipuk]

Rendered

Signed-off-by: Tom Foster tom@tcpip.uk

---

Known Implementations:

• Clients:
• Servers:

---

SCT Stuff:

No MSC checklist

FCP close tickyboxes

[tcpipuk]

This MSC is dependent on #3843 to allow users to report inappropriate users (e.g. offensive MXID, or inappropriate user profile content) rather than a specific event.

[tulir]

Implementation requirements:

• Client

(as this MSC depends on #3843, a server implementation is only needed for that MSC and not this one)

[MTRNord]

One to add is that this might (as like with most moderation things on server level) have the issue that server and room rules may differ. A profile might be considered ok by the server admin, while it isn't ok for the room where the user is in. So this proposal only adds server level moderation but still no full room level moderation imho. It solves parts of the issues, but not all of them, imho.

[tcpipuk]

Agreed, do you know if there's an MSC for reporting events to room admins so I could perhaps add that as a dependency here too?

[turt2live]

With my Foundation T&S hat, we're looking at redesigning how reporting works in Matrix to support better communication and be more actionable. With that in mind, we've opened a proposal to generify the reporting API that we're currently working on implementing: #4457

It's become clear as part of planning Reporting v2 that having dedicated endpoints for each type of report is unwieldy and leads to inconsistencies with relative ease.

With my SCT hat, I'm suggesting we close this in favour of MSC4457 or something very near to it (single endpoint rather than many).

@mscbot fcp close

Note: We typically try to reach out to the author out of band before proposing an MSC for closure, but in this case I couldn't find the author's account in the spec rooms to have that conversation. Proposal authors are not required to wait for FCP to start/finish before closing their proposals if they don't want to.

[mscbot]

Team member @turt2live has proposed to close this. The next step is review by the rest of the tagged people:

• @clokep
• @dbkr
• @uhoreg
• @turt2live
• @ara4n
• @anoadragon453
• @richvdh
• @tulir
• @erikjohnston
• @KitsuneRal

Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for information about what commands tagged team members can give me.