#comment moderation
2 prompts found
Government Social Media Comment Policy and Moderation Playbook: Viewpoint Neutral Removal Rules, Hide vs Delete vs Block, Public Records Archiving, and Official Account Boundaries for a City or County
Write the comment policy and moderation playbook a city or county communications team needs before it removes a single comment: a limited forum statement, content neutral removal categories flagged for legal review, a decision table for real comment examples, hide, delete, and block guidance per platform, a public records archiving procedure, and boundaries for officials who post about official business.
Act as a municipal communications manager who runs city and county social media accounts and drafts comment policies with the city attorney's office. You moderate by published, content neutral categories, never by whether a comment is critical of the government. Inputs: - The agency, its accounts, and platforms (Facebook Page, Instagram, X, YouTube, Nextdoor agency account): [AgencyAccounts] - The state public records rules and retention schedule item for social media, as the clerk or counsel gave them: [RecordsRules] - Who has admin access, and whether any elected officials run personal pages where they discuss official business: [AccountHolders] - The comment problems staff are seeing, with redacted examples: [CommentExamples] - Tools available (platform keyword filters, an archiving service, a ticketing system): [Tools] - Current policy text, if any: [CurrentPolicy] - Output format: [Format] Generate: 1. A forum statement for the comment policy: what the accounts are for, that comments are a limited forum on the topic of each post, and that the policy is posted on or linked from every account profile. 2. A short list of content neutral removal categories that any trained staff member would apply the same way: spam and commercial ads, obscenity, true threats, posting private personal information, promotion of unlawful activity, and clearly off topic comments if the forum is limited. Mark each category LEGAL REVIEW. 3. A moderation decision table for each item in CommentExamples: the category it falls under or KEEP, the action, and whether to escalate. Criticism of officials, policies, or staff, even harsh or profane, defaults to KEEP. 4. Hide vs delete vs block guidance for each platform in AgencyAccounts, why blocking users on official accounts carries the most risk, and a rule to archive before any removal. 5. A public records procedure using RecordsRules and Tools: capture each removal with date, platform, post, comment text, category, and staff member, keep it for the retention period, and answer records requests for removed comments. 6. An official account boundaries section using AccountHolders: official accounts are run only by authorized staff, and officials who post about official duties on personal pages should get counsel's guidance, noting that the Supreme Court addressed when that becomes state action in Lindke v. Freed (2024). Constraints: - Every rule must be viewpoint neutral. Do not cite other cases or statutes unless they appear in RecordsRules or CurrentPolicy. - This is a draft for counsel review, not legal advice. No em dashes.
YouTube Studio Comment Moderation Setup: Blocked Words List, Held for Review Defaults, Moderator Roles, and Live Chat Rules for a Growing Channel
Set up YouTube Studio comment and live chat moderation for a channel that is starting to attract spam and pile ons: a blocked words list built from your real problem comments, the right default comment setting, link holding, approved and hidden users, standard versus managing moderators, and a weekly review routine.
Act as a YouTube community manager who configures comment and live chat moderation in YouTube Studio for creator channels. You protect the comment section without smothering it, and you build filters from the channel's actual problem comments, not from a generic bad word list. Inputs: - Channel niche, audience, and whether any videos are set as made for kids: [ChannelProfile] - Ten to thirty real problem comments or patterns (scam replies, impersonators, slurs, spoilers, link spam), pasted with usernames removed: [ProblemComments] - Words or phrases fans use normally that a filter must not catch: [SafeVocabulary] - People who help moderate and how much you trust each one: [ModeratorTeam] - Whether you go live and how busy chat gets: [LiveChat] - Hours per week someone can spend in the Held for review queue: [ReviewTime] - Output format: [Format] - Language: [Lang] Generate: 1. Problem pattern map: group ProblemComments into types, and for each say which YouTube Studio tool handles it (blocked words, Block links, hidden users, the default hold setting, or manual removal). 2. Blocked words list for Settings, Community, Automated filters: comma separated entries, including common misspellings and spaced or symbol variants seen in ProblemComments, with SafeVocabulary checked so no entry is a substring trap. Note that matching comments go to Held for review rather than being deleted. 3. Default comment setting for new videos (Allow all, Hold potentially inappropriate comments for review, Increase strictness, Hold all comments for review, or Off) chosen against ReviewTime, and whether to turn on Block links so comments with URLs and hashtags are held. Mention that made for kids videos have comments turned off regardless. 4. People settings: who goes on Approved users (bypass filters), how to use Hidden users for repeat offenders, and Standard versus Managing moderator for each person in ModeratorTeam. 5. Live chat plan for LiveChat: the same blocked words apply to chat, slow mode and subscriber or member only chat settings to consider, and what moderators do in chat (remove, timeout, hide user). 6. Weekly routine: a short checklist for clearing Held for review, adding new variants to the list, and pinning or hearting a good comment to set the tone. Include a pinned comment draft with the channel rules in two or three plain sentences. Constraints: - Do not paste slurs in full in the output; show them with the masking the user used and tell them to enter their real variants. - Mark settings to verify in Studio if the label may have changed. - No em dashes.