Requests is the unified inbox for abuse reports, DMCA notices, and general contact messages.

• abuse reports
• DMCA reports
• contact messages

• top queue filters for All, Archive, Contact, DMCA, and Abuse
• a small status filter for narrowing the current queue
• expandable request rows with full detail, workflow tools, and activity
• direct reply tools for Contact and DMCA items
• moderation actions for Abuse items

• review new requests quickly
• keep moderation queue counts low
• use the combined request flow when triaging work
• preserve notes for sensitive or repeat issues

Recommended flow:

1. filter by request type first
2. open the item and read the full body or target links
3. add an internal note before handoff
4. reply from the request record if the item is Contact or DMCA
5. change status only after the real review step, not just because the item was opened

• Contact uses New, Read, Replied, and Closed
• DMCA uses Pending, Investigating, Resolved, and Rejected
• Abuse uses Pending, Reviewed, Action Taken, and Dismissed
• archive behavior is driven by the final status for that request type

DMCA items now include a dedicated Process Removal of Files card inside the expanded request view.

What it does:

• normalizes submitted DMCA target URLs
• tries to match each URL to a local fyuhls file
• lets you process checked files only, or all matched files at once
• disables URLs that do not match a local file or are already removed or pending purge
• records the file-removal action back into the same request activity stream

Important behavior:

• processing happens inline without a full page refresh
• the file rows update immediately after success
• the Activity section is updated live with the removal event
• the removal reason is stored in a generic compliance-safe way instead of baking the request number into the file-removal reason

Use this when you want the compliance record and the actual file-removal action to stay attached to the same DMCA item.

Practical operator flow:

1. open the DMCA request
2. verify the target links
3. process selected files or process all matched files
4. leave an internal note if anything was skipped or manually reviewed
5. update the request status after the actual removal step is complete

Public abuse, DMCA, and contact flows are rate-limited more directly now than older versions.

Turnstile placement for Contact, Abuse, and DMCA lives under:

• Config Hub > Security > Captcha

The Requests inbox itself is meant to keep support, abuse, and DMCA in one place so operators do not need a separate mental model for every incoming queue.

• Config Hub Reference
• System Status and Diagnostics
• Rewards Fraud