Mastodon: Workflow for DMCA takedowns (and reinstatements)

[lofidevops]

User story: I am the admin on a Mastodon instance. When I receive a DMCA takedown request, I want to be able to reverse the takedown process, so that I can easily support a successful challenge.

• [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate. https://github.com/tootsuite/mastodon/issues/9 and https://github.com/tootsuite/mastodon/issues/1847 are related, but don't make it clear what the workflow (if any) is for re-instating a toot after it is taken down.

Background:

In the event of a DMCA takedown request, the operator must comply with the request immediately. However, the user has the option to challenge the request and, if successful, reinstate the uploaded content. (This approach applies to other existing and future laws that operate on a shoot-first-go-to-court-later principle.)

Suggested solution:

1. User posts toot
2. Copyright holder complains to operator
3. Operator hides toot, informs user
4. Option A: User accepts decision, deletes toot
5. Option B: User ignores event, toot remains hidden
6. Option C: User challenges copyright holder, loses: see A or B
7. Option D: User challenges copyright holder, wins, operator un-hides toot

I suspect that steps 3 and 7 need to be implemented and/or documented.

Options for "hiding":

• original toot is simply deleted
• original toot is stored on server but not displayed
• original toot is stored on server but modified version is displayed (reads "REMOVED" or a custom message like "REMOVED AT THE REQUEST OF [NAME]")
• original toot is replaced with "REMOVED" message, and no longer stored on server (re-instatement is not possible, user must re-toot)

Options for federation:

• applies to each instance independently (copyright holder has to find all copies and contact each instance that displays the toot, reinstatement will not propagate)
• origin operator transmits changes (hide and un-hide signals) both upstream and downstream -- no guarantee that other instances can or will honor the signal

[Gargron]

We need soft-deletes for this, see also: #5760