nether/meta

Scenario Play Book #11

New issue

Open

opened 2026-07-12 00:08:33 +00:00 by dark · 1 comment

dark commented

2026-07-12 00:08:33 +00:00

Owner

Forewarned is forearmed. Or something...I dunno I heard it in Dead Space.

Anyway, so we should really start setting up our moderation tooling before horrible things happen. We should set up mjolnir, policy servers, and other tools (if they're compatible with tuwunel). And we should subscribe to banlists after verifying them.

I think we also need to create a playbook for emergencies. If a user is threatening suicide, or someone is spamming us with CSAM, or we're getting defederated for a misunderstanding, we don't want to try to invent protocols on the fly, we (and by we I mean the moderation team) want already have a step by step guidebook for how to respond.

Forewarned is forearmed. Or something...I dunno I heard it in Dead Space. Anyway, so we should really start setting up our moderation tooling _before_ horrible things happen. We should set up mjolnir, policy servers, and other tools (if they're compatible with tuwunel). And we should subscribe to banlists after verifying them. I think we also need to create a playbook for emergencies. If a user is threatening suicide, or someone is spamming us with CSAM, or we're getting defederated for a misunderstanding, we don't want to try to invent protocols on the fly, we (and by we I mean the moderation team) want already have a step by step guidebook for how to respond.

dark added the

labels

2026-07-12 00:08:33 +00:00

dark changed title from ~~Scenario Play Book / Moderation Tooling~~ to Scenario Play Book

2026-07-12 03:18:20 +00:00

robocub commented

2026-07-12 16:35:48 +00:00

Member

Related direction in #21: runbooks proposed as literate org files living in the infrastructure repo — node resurrection = guix system init + state restore, executable by any trusted member — with a longer-term warden bot executing runbook steps on human ack in the ops room. This issue is effectively the seed of that runbook collection.

Related direction in #21: runbooks proposed as literate org files living in the infrastructure repo — node resurrection = `guix system init` + state restore, executable by any trusted member — with a longer-term warden bot executing runbook steps on human ack in the ops room. This issue is effectively the seed of that runbook collection.

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

nether/meta#11

No description provided.

Rows
Columns