RunicGateway/docs
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: plan report/block/hide, decide M8's open items, plan demo content #390

Merged
whitlocktech merged 4 commits from docs/report-block-hide-plan into main 2026-10-29 08:10:04 -05:00
Conversation 0 Commits 4 Files Changed 4 +289 -14
wtclaude commented 2026-10-29 07:27:38 -05:00
Member
Copy Link

Records the org lead's 2026-10-29 answers and the plans that follow from them. No code yet. Each piece stops for approval.

What's in it

  • website/USER_SAFETY.md (new): report, block and hide on the website and in the app.

    • S1-S5 are decided: keep the content rating and make it true; a block lives on the account and applies everywhere; members can hide an item for themselves and staff can hide it for everyone; the app gets chat lines now and the forum later; the cutover waits for this feature.
    • Design: modules declare their own report targets (reportTargets, MODULE_API 1.20.0), reports store a snapshot of the reported item, and the queue gains Hide for everyone. New user_blocks (an account or a game identity such as a Steam ID) and user_hidden_items tables.
    • §5 holds five questions for the org lead (signed-out reporting, blocking unlinked Steam IDs, blocking staff, what a block does to the blocked person, staff's view of hidden chat).

  • android/PLAN.md M8: the three open items are decided.

    • Conservative data-safety answers.
    • UnifiedPush moves to the specialUse service type and restarts after a reboot. This also fixes a crash: on Android 15+ with target 36, the current dataSync service is cut off after six hours a day and never handles the timeout.
    • The order to the cutover, with the org lead enrolling the signing key before it merges.
    • M21, Teams and the team forum in the app, is planned but not scheduled.

  • website/DEMO_MODE.md: DM32 and §11, the demo content plan.

    • Two seed passes, because Teams are owned by the module and only appear after the rig syncs.
    • Moderation history, Teams with forum and reports, event history with the calendar, and Rust player stats.
    • §11.3 has three questions: stand-in Steam IDs that might belong to real people, invented Discord IDs, and names.

  • AI-assisted (Claude Code)

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

Records the org lead's 2026-10-29 answers and the plans that follow from them. **No code yet.** Each piece stops for approval. ## What's in it - **`website/USER_SAFETY.md` (new)**: report, block and hide on the website and in the app. - S1-S5 are decided: keep the content rating and make it true; a block lives on the account and applies everywhere; members can hide an item for themselves and staff can hide it for everyone; the app gets chat lines now and the forum later; the cutover waits for this feature. - Design: modules declare their own report targets (`reportTargets`, `MODULE_API` 1.20.0), reports store a snapshot of the reported item, and the queue gains *Hide for everyone*. New `user_blocks` (an account or a game identity such as a Steam ID) and `user_hidden_items` tables. - **§5 holds five questions for the org lead** (signed-out reporting, blocking unlinked Steam IDs, blocking staff, what a block does to the blocked person, staff's view of hidden chat). - **`android/PLAN.md` M8**: the three open items are decided. - Conservative data-safety answers. - UnifiedPush moves to the `specialUse` service type and restarts after a reboot. This also fixes a crash: on Android 15+ with target 36, the current `dataSync` service is cut off after six hours a day and never handles the timeout. - The order to the cutover, with the org lead enrolling the signing key before it merges. - **M21**, Teams and the team forum in the app, is planned but not scheduled. - **`website/DEMO_MODE.md`**: DM32 and §11, the demo content plan. - Two seed passes, because Teams are owned by the module and only appear after the rig syncs. - Moderation history, Teams with forum and reports, event history with the calendar, and Rust player stats. - §11.3 has three questions: stand-in Steam IDs that might belong to real people, invented Discord IDs, and names. - [x] AI-assisted (Claude Code) 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-29 07:27:41 -05:00
docs: plan report/block/hide, decide M8's open items, plan demo content df3d43f355 
- website/USER_SAFETY.md (new): report, block and hide on the website and
  in the app, S1-S5 decided by the org lead, five questions open.
- android/PLAN.md: M8's three open items decided (keep the rating and add
  report/block/hide; conservative data safety; UnifiedPush on specialUse
  with restart on boot), the order to the cutover, and M21 (Teams and the
  team forum in the app, planned, not scheduled).
- website/DEMO_MODE.md: DM32 and section 11, the demo content plan (two
  seed passes; moderation, Teams/forum/reports, event history, Rust stats).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-29 07:34:21 -05:00
docs: record the org lead's answers on report/block/hide and demo identities 499a686bf3 
- USER_SAFETY.md: section 5 becomes decisions S6-S10 (an account to report,
  game-identity blocks allowed, staff cannot be blocked, a block only hides,
  staff see hidden chat marked).
- DEMO_MODE.md: DM33-DM35 (visibly fake 1234567890-prefixed Steam and
  Discord ids plus the org lead's own Steam id; Rust-themed invented names).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-29 07:48:26 -05:00
docs(android): record M8 step 1, the push fix, as built (Android-app#62) 0485dcc87e 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-29 08:09:18 -05:00
docs(demo): confirm DM33 (the org lead's Steam ID as demo-player's link) and DM34 cd6d3d3b8a 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
whitlocktech merged commit 410c8acfe6 into main 2026-10-29 08:10:04 -05:00
whitlocktech deleted branch docs/report-block-hide-plan 2026-10-29 08:10:05 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ksfixitman whitlocktech wtclaude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RunicGateway/docs#390
No description provided.
Delete Branch "docs/report-block-hide-plan"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?