t5de/t5de-hub
2
0 Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases 1 Wiki Activity

feat: cases (reports, reviews, requests, appeals) and notifications #9

Merged
dhkatz merged 1 commits from feat/cases into main 2026-11-05 22:14:08 +00:00
Conversation 0 Commits 1 Files Changed 33
+5228 -44
dhkatz commented 2026-11-05 15:04:41 +00:00
Owner
Copy link
Copy source

Phase 3, part 1 (docs/design.md, "Next"): cases and notifications. File blocks, API tokens and two-factor sign-in come as separate PRs.

Cases

  • One queue (Console → Cases) for everything someone has to decide. Each case has:
    • a thread of notes, where internal notes are visible only to those deciding
    • an assignee (moderators assign cases to moderators)
    • a decision, Resolve or Decline, with a written resolution that the person who opened it sees
  • Reports: anyone signed in can report a product or catalog from its page (the API also takes rooms and people).
    • Limits: 10 an hour, one open report per person and thing, and you can't report yourself.
    • Reports about a product go to the teams of the catalogs hosting it, as well as to moderators.
    • Only the reporter and moderators know who reported. The audit entry for a report isn't tagged with what it's about, so a product's creator can't find out from their audit log either.
  • Rating reviews: a creator lowering a rating from adult to general now opens a review instead of being refused. The rest of the edit still saves. Resolving the review lowers the rating, recorded in the product's history.
  • Removal requests: a catalog's team can ask moderators to remove a product it hosts, everywhere. Resolving it removes the product.
  • Deletion requests: a catalog's owner asks for deletion from the catalog's console page, and a moderator decides, as agreed. Resolving it marks the catalog deleted: its key stops working, nothing is available from it, and its changes feed says so.
  • Appeals:
    • From the audit log, the person an action affected can appeal it, once: their product removed, delisted or edited by someone else; their catalog suspended or rejected; a ban from a catalog or a declined request to join.
    • Another moderator decides. An admin may decide an appeal of their own action, and the audit log flags it.
    • Resolving records the decision; the moderator then undoes the action where it's done. For that, there's now a Restore for removed products (Console → Products, for moderators); the design mentioned one, but it was never built.
  • The console shows a "Cases" tab, and a to-do with the number of open cases the person could decide.

Notifications

  • A bell in the header with the unread count, and a notifications page with "Mark all as read".
  • Each is also sent to the person's proxies over the realtime connection ({"type": "notification"}), so the client can show them later.
  • They cover:
    • a moderator edited or locked your product, or undid a change (with the reason)
    • your product was removed or restored
    • your case was decided
    • someone replied on your case
    • a catalog decided your membership

Also changed

  • A product's creator and moderators can now see it when it's adult, even without an adult account. Before, a creator who made their own product adult couldn't open its page any more, and neither could moderators. Getting and wearing adult products still need an adult account.

Not done yet (in docs/console.md): email notifications (the hub sends no email yet), canned reasons, private moderator notes on people and products, and second approval for the most destructive actions.

Migration 0012_cases: the moderation_case, case_note and notification tables. (case is a reserved word in SQL, hence the table's name.)

Checks

  • 51 API tests pass. The 7 in the new cases.test.ts cover:
    • who sees and decides each kind of case, and that the reporter stays private
    • rate limits and duplicate reports
    • the thread and internal notes, and assigning
    • what deciding each kind of case does
    • appeals by the person affected only, decided by another moderator
    • restoring a removed product
    • the notifications
  • Type checks pass.
  • On a local hub I went through every flow with the website's own forms: report from a product page; the catalog owner's note and decision; assigning, an internal note and a decision as admin; removal by a moderator, the creator's appeal from the audit log, the admin's decision and Restore; a creator's rating review and the decision lowering the rating; a deletion request and its decline; the notifications, the bell's count, and Mark all as read.
  • Fixed along the way:
    • The catalog's team could see who reported.
    • A missing Resolve/Decline choice was treated as Decline; now it's refused.
    • The Unassign button sent the typed name instead of nothing.

🤖 Generated with Claude Code

Phase 3, part 1 (`docs/design.md`, "Next"): cases and notifications. File blocks, API tokens and two-factor sign-in come as separate PRs. **Cases** - One queue (Console → Cases) for everything someone has to decide. Each case has: - a thread of notes, where internal notes are visible only to those deciding - an assignee (moderators assign cases to moderators) - a decision, Resolve or Decline, with a written resolution that the person who opened it sees - **Reports:** anyone signed in can report a product or catalog from its page (the API also takes rooms and people). - Limits: 10 an hour, one open report per person and thing, and you can't report yourself. - Reports about a product go to the teams of the catalogs hosting it, as well as to moderators. - Only the reporter and moderators know who reported. The audit entry for a report isn't tagged with what it's about, so a product's creator can't find out from their audit log either. - **Rating reviews:** a creator lowering a rating from adult to general now opens a review instead of being refused. The rest of the edit still saves. Resolving the review lowers the rating, recorded in the product's history. - **Removal requests:** a catalog's team can ask moderators to remove a product it hosts, everywhere. Resolving it removes the product. - **Deletion requests:** a catalog's owner asks for deletion from the catalog's console page, and a moderator decides, as agreed. Resolving it marks the catalog `deleted`: its key stops working, nothing is available from it, and its changes feed says so. - **Appeals:** - From the audit log, the person an action affected can appeal it, once: their product removed, delisted or edited by someone else; their catalog suspended or rejected; a ban from a catalog or a declined request to join. - Another moderator decides. An admin may decide an appeal of their own action, and the audit log flags it. - Resolving records the decision; the moderator then undoes the action where it's done. For that, there's now a Restore for removed products (Console → Products, for moderators); the design mentioned one, but it was never built. - The console shows a "Cases" tab, and a to-do with the number of open cases the person could decide. **Notifications** - A bell in the header with the unread count, and a notifications page with "Mark all as read". - Each is also sent to the person's proxies over the realtime connection (`{"type": "notification"}`), so the client can show them later. - They cover: - a moderator edited or locked your product, or undid a change (with the reason) - your product was removed or restored - your case was decided - someone replied on your case - a catalog decided your membership **Also changed** - A product's creator and moderators can now see it when it's adult, even without an adult account. Before, a creator who made their own product adult couldn't open its page any more, and neither could moderators. Getting and wearing adult products still need an adult account. **Not done yet** (in `docs/console.md`): email notifications (the hub sends no email yet), canned reasons, private moderator notes on people and products, and second approval for the most destructive actions. **Migration** `0012_cases`: the `moderation_case`, `case_note` and `notification` tables. (`case` is a reserved word in SQL, hence the table's name.) **Checks** - 51 API tests pass. The 7 in the new `cases.test.ts` cover: - who sees and decides each kind of case, and that the reporter stays private - rate limits and duplicate reports - the thread and internal notes, and assigning - what deciding each kind of case does - appeals by the person affected only, decided by another moderator - restoring a removed product - the notifications - Type checks pass. - On a local hub I went through every flow with the website's own forms: report from a product page; the catalog owner's note and decision; assigning, an internal note and a decision as admin; removal by a moderator, the creator's appeal from the audit log, the admin's decision and Restore; a creator's rating review and the decision lowering the rating; a deletion request and its decline; the notifications, the bell's count, and Mark all as read. - Fixed along the way: - The catalog's team could see who reported. - A missing Resolve/Decline choice was treated as Decline; now it's refused. - The Unassign button sent the typed name instead of nothing. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
dhkatz added 1 commit 2026-11-05 15:04:41 +00:00
feat: cases (reports, rating reviews, removal and deletion requests, appeals) and notifications
Pull request / title (pull_request) Successful in 1s
Details
CI / test (pull_request) Successful in 1m5s
Details
CI / image (apps/api/Dockerfile, t5de-hub-api) (pull_request) Skipped
Details
CI / image (apps/web/Dockerfile, t5de-hub-web) (pull_request) Skipped
Details
8af4b7b6a9 
Cases are one queue for what someone has to decide, each with a thread (internal notes for those deciding), an
assignee and a decision. Reports about a product go to the teams of the catalogs hosting it and to moderators, and
only the reporter and moderators know who reported. A creator lowering a rating opens a rating review; a catalog's
owner asking to delete it opens a deletion request; a catalog's team can ask for a product's removal everywhere; the
person an action affected can appeal it once, decided by another moderator (an admin may decide their own, flagged).
Resolving carries the case out: the rating is lowered, the product removed, the catalog deleted.

Notifications reach people on the website (a bell with the unread count) and their proxies (realtime): moderators'
edits to their products, removals and restores, decisions and replies on their cases, membership decisions.

Also: moderators can restore a removed product, and a product's creator and moderators can see it when it's adult
without an adult account (getting and wearing it still need one).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
dhkatz merged commit 7299e10b08 into main 2026-11-05 22:14:08 +00:00
dhkatz deleted branch feat/cases 2026-11-05 22:14:08 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
deploy dhkatz release-bot (Release bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t5de/t5de-hub#9