Add tracking of the source of a report

[ThisIsMissEm]

Problem being solved

Currently all reports look alike, even though they can originate from different places within the users' application. The API for creating a report currently takes in:

• the reporter
• the report date
• the reason (free text, policy, and a csam flag)
• the reported items and their threads
• additional items

In addition we should probably capture from where in the app content was reported from (a configurable enum), for instance it may be from a feed, from a user profile, or from the post itself.

Having this context can help surface when people are going directly to the account to report vs reporting individual content.

Proposed solution

Add a field for report source, which is a configured set of options that integrators can then integrate against. This allows for providing additional context in a programmatic sense which can help analysts understand why reports aren't being actioned.

This information should probably also have the ability to track a "user-agent" type string to correlate reports coming from different applications or integrations with the service provider.

Alternatives considered

I don't think there is any alternative, other than perhaps correlating to an analytics session id?

Anything else

This issue was inspired by recent conversation in the mastodon discord, where low quality reports where coming through because client software had not implemented adequate reporting flows.

Screenshots

No response

Checklist

• I’ve reviewed and agree to follow the code of conduct

[reitblatt]

The overall idea makes perfect sense to me: this was something that we found incredibly useful at Meta to identify regressions in coverage across mobile versions, platforms, etc. It's also useful to identify abusive/scripted reporting.

I suspect over time you'll find you want much richer features beyond just reporting surface, so we should probably plan for this up front. I still don't have coop fully in my head, so do you have any ideas how to design for that, while also making the easy case (e.g. initially just a reporting surface enum) easy?