New moderation and report processing flow

[jonasfj]

The things we have to do are:

• Moderation actions:

  • Introduce moderatedAt and isModerated on
    • Package
    • PackageVersion
    • Publisher
    • User
  • Enforce moderated semantics for:
    • Package (not available in API, public bucket, search, and web page says moderated)
    • PackageVersion (not available in API, public bucket, and web page says moderated)
    • Publisher (web page says moderated, packages owned by publisher can't be updated)
    • User (can't sign-in on pub.dev or publish using dart pub; packages owned exclusively by the user are marked discontinued)
  • Administrative actions to:
    • Set or clear Package.isModerated/moderatedAt
    • Set or clear PackageVersion.isModerated/moderatedAt
    • Set or clear Publisher.isModerated/moderatedAt
    • Set or clear User.isModerated/moderatedAt
    • Add optional case tracking: --case=<caseId> (use --case=none)
    • Add optional email-body for content-owners
  • Periodic task to delete entities and associated resources if now() - moderatedAt > 3 years
    (users are still just user.isDeleted = true with Likes being deleted).

• In-take report form

  • content about the process and what to expect
  • form submitting + processing
  • linking from public pages
  • setup deep linking for other systems

• notifications

  • confirmation emails on form submission
  • notification emails on case resolution (with appeal-link)
  • notification emails on restrictive action (with appeal-link)

• Tracking cases

  • List active cases
  • Create case with source = notification | trusted-flagger | authorities | legal-referral
  • Close an active case
  • Modify a case (including status)

• Tracking user account moderation / blocked / suspended

  • When a user was moderated
  • Why the user was moderated: reason = illegal-content | policy-violation | unfounded-notifications | unfounded-appeals
    This will be extremely rare, we can probably track this with properties on the User entity.

• statistical reporting

---

Implementation details of isModerated/moderatedAt

To ensure that we reverse moderation decisions, we're going to add properties:

• isModerated, true, if moderated, otherwise false, and,
• moderateAt, date-time when entity was moderated, otherwise null.

We are adding these properties to the following entities:

• Package,
• PackageVersion,
• Publisher, and,
• User.

With the effect that being moderated means that:

• Entity is not visible in API
• Entity is not visible on website, if direct URL for the entity is accessed a message will state that it was moderated.
• Entity is not available in search (not even with include:unlisted).
• Entity can't be used for authentication or authorization, meaning
  • A moderated user can't sign-in, and,
  • Packages of a moderated publisher can't be updated.

We'll default to deleting entities and related resources 3 years after moderatedAt.

When setting isModerated on Publisher or User this can cause packages that are solely owned by said entity to be marked as isDiscontinued. When clearing isModerated we do not change this back, it's simply too much information to track.

[jonasfj]

@isoos can we implement:

Periodic task to delete entities and associated resources if now() - moderatedAt > 3 years
(users are still just user.isDeleted = true with Likes being deleted).

Ideally, next week.

[isoos]

Closing as we seem to completed all pending tasks.