eric/gitlab-instance-0a899031_nomadro
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add nomadro.live English WordPress stack and audience router

Browse Source 
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
eric
2026-08-24 04:35:48 -05:00
parent 0e997576c1
commit 7a9365480e
36 changed files with 1100 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
deploy/nomadro-live/wordpress/content/posts/07-chat-moderation-workflow.html Normal file
View File

@@ -0,0 +1,11 @@
<p>Chat moderation during a live is a workflow, not a personality trait. Teams that skip the workflow either freeze on insults or over-block and kill the room.</p>
<h2>Write the rules before the show</h2>
<p>List banned topics, allowed teasing, and what happens on repeat offenses. If two moderators would disagree, the rule is not written yet.</p>
<h2>Keyword alerts versus bans</h2>
<p>Alerts are for review. Auto-hide is for unambiguous spam. Mixing them causes either alert fatigue or silent over-moderation. Keep the lists separate and short.</p>
<h2>Escalation</h2>
<p>First offense: hide or timeout. Second: longer timeout. Third: block and a one-line note in the session log. Skipping steps makes appeals impossible.</p>
<h2>On-camera coordination</h2>
<p>The host should not read every flagged line. Moderators send a three-word cue when the host must address something. Long Slack essays during a live are a failure mode.</p>
<h2>Aftercare</h2>
<p>Export flagged messages with timestamps. Review once, adjust the keyword list, and stop relitigating the same clip in group chat for three days.</p>