AGENT SKILL

social-moderation-abuse-and-regulation

Use when handling harmful content or a compliance requirement: moderation at scale (classifiers, human review queues, appeals, policy design, reviewer welfare), spam, bots and abuse engineering (rate limits, reputation, coordinated behaviour detection, account takeover), and the regulatory layer — the DSA, the Online Safety Act, age assurance and where enforcement is actually landing.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 5
Forks
3

01 前言 Front Matter

name
social-moderation-abuse-and-regulation
description
Use when handling harmful content or a compliance requirement: moderation at scale (classifiers, human review queues, appeals, policy design, reviewer welfare), spam, bots and abuse engineering (rate limits, reputation, coordinated behaviour detection, account takeover), and the regulatory layer — the DSA, the Online Safety Act, age assurance and where enforcement is actually landing.

03 SKILL.md 正文

Social Media Engineering: Moderation at Scale, Spam and Abuse, and Regulation

Part 3 of 5 of the Social Media Engineering reference (plugin social-media-engineering), covering §7–§9. Sibling skills: social-platform-apis-and-open-protocols (§0–§2), social-feed-graph-ranking-and-notifications (§3–§6), social-media-analytics-privacy-and-presence (§10–§13), social-reference (§14–§19). Section numbers are shared across the set; a reference written as §N → skill points into that sibling skill.

Currency: Verified August 2026. See §16 → social-reference for the currency snapshot and what goes stale first.

How to read this. The title spans two things and this document covers both, weighted toward the first: §1–§12 → social-platform-apis-and-open-protocols, social-feed-graph-ranking-and-notifications, social-media-analytics-privacy-and-presence are about building and integrating with social systems; §13 → social-media-analytics-privacy-and-presence is about your own presence as a developer. Skip to §13 → social-media-analytics-privacy-and-presence if that's what you came for.

Three markers:

  • [DURABLE] — architecture, ranking, moderation, and abuse dynamics. Most of §2–§10 → social-platform-apis-and-open-protocols, social-feed-graph-ranking-and-notifications, social-media-analytics-privacy-and-presence.
  • [VERSIONED] — platform terms, pricing, protocols, regulation. ⚠️ Verify all of it; this is the fastest-moving material in the collection after AI.
  • [CONTESTED] — genuine disagreement.

⚠️ GOTCHA boxes mark what breaks, gets you banned, or gets you fined.

The three framings that organize everything below:

  1. ⚠️ Building on a platform API is building on rented land, and the rent changed. The 2023–2026 period established that platforms will reprice or withdraw access with weeks of notice and no obligation. Architect for that from day one (§1 → social-platform-apis-and-open-protocols).
  2. The hard problems are social, not technical. Fan-out and ranking are solved engineering; moderation, abuse, and incentive design are not, and they scale worse than your database does (§7, §8).
  3. ⚠️ Compliance is now an architecture input, not a legal afterthought. Age assurance, transparency reporting, and appeals mechanisms have to be designed in — and regulators have started saying explicitly that self-declaration is not sufficient (§9).

§7. Moderation at Scale

[DURABLE] The hardest problem in this document, and the one engineering can only partially address.

The layered pipeline everyone converges on:

1. PREVENTION      rate limits, friction, account age gates, verification
2. AUTOMATED       hash matching (PhotoDNA/CSAM, known-violating media),
                   classifiers, heuristics
3. USER REPORTING  with abuse-of-reporting handling and prioritization
4. HUMAN REVIEW    queues, tooling, escalation
5. APPEALS         ⚠️ now legally required in the EU (§9)
6. TRANSPARENCY    reporting, also legally required

⚠️ The realities that break naive designs:

  • Scale: at any real volume, human review of everything is impossible and automation alone is inadequate. You will build a triage system, so design it deliberately.
  • Context: the same words are abuse or reclamation depending on speaker, audience, and history. ⚠️ Classifiers do not have that context.
  • Adversaries adapt — every filter is a spec for evading it (§8).
  • ⚠️ Reviewer welfare is a real duty of care. Exposure to violent and abusive content causes documented psychological harm; rotation, counselling, blurring by default and volume limits are not optional if you employ or contract reviewers.
  • Cultural and linguistic coverage — ⚠️ most systems are dramatically weaker outside English, and this is where the most serious real-world harms have occurred.
  • False positives have real costs to real people, and appeals must actually work.

[DURABLE] The structural point: CSAM detection has legal mandatory-reporting obligations (NCMEC in the US) and hash-matching participation is effectively expected; terrorism and violent extremism have their own regimes; and ⚠️ "we're too small to need moderation" stops being true the moment you're large enough to be worth abusing — which is much sooner than most teams plan for.


§8. Spam, Bots, and Abuse

[DURABLE] Adversarial engineering — assume a motivated opponent who reads your documentation.

The attack surface: bulk account creation, coordinated inauthentic behaviour (⚠️ the hard one — individually plausible accounts acting in concert), engagement farming, scraping (see a web-scraping reference), impersonation, phishing in DMs, spam in replies and mentions, brigading and targeted harassment, and vote or metric manipulation.

Defences, roughly in order of value: friction at signup (email/phone verification, ⚠️ and an awareness that this trades against accessibility and privacy), rate limiting per account, per IP, per device, and per behaviour pattern, behavioural signals over content signals (⚠️ timing, sequence, and network structure are much harder to fake than text), graph analysis for coordination — clusters behaving identically are the signal — device and browser fingerprinting (privacy trade-off, and increasingly regulated), shadow-limiting rather than hard blocking (⚠️ so the adversary doesn't learn immediately that they were caught — though this is ethically contested when applied to real users), and reputation systems that decay.

⚠️ And the AI-era additions: generated content at volume is cheap now, which breaks detection heuristics built on "does this look human-written"; and provenance signals (C2PA and similar) are the direction of travel but not yet dependable.


§9. Regulation and Compliance

[VERSIONED — and this now determines what you may ship.]

9.1 The regimes

EU Digital Services Act. ⚠️ Applies if you operate in the EU or have a "substantial connection" to it — headquarters elsewhere does not exempt you, and non-EU providers must nominate a legal representative. Enforcement is split: the Commission handles VLOPs; national Digital Services Coordinators handle everyone else. Obligations include user-friendly illegal-content reporting, a ban on targeted advertising to minors, statements of reasons when content is restricted, an internal appeals system, annual transparency reporting, and law-enforcement notification for potential criminal activity.

UK Online Safety Act. ⚠️ "Highly effective age assurance" required from July 2025 for services exposing under-18s to harmful content. Ofcom accepts photo-ID matching, facial age estimation, Open Banking, digital identity services, and mobile-network checks — ⚠️ self-declaration alone is explicitly not sufficient. Penalties reach up to 10% of global turnover.

US: no federal age-verification law as of mid-2026, but more than a dozen states have enacted requirements. Australia has an active regime with penalties up to AUD $49.5M.

9.2 ⚠️ Enforcement is real and it's landing on age assurance

This is the part that has changed most, and the direction is unambiguous:

  • The UK ICO fined Reddit £14.5 million in early 2026 for failing to adequately protect children's data and relying heavily on self-declaration.
  • Ofcom has fined adult sites for lacking "highly effective" age assurance.
  • The Commission preliminarily found Meta in breach (April 2026) for failing to prevent under-13s accessing Facebook, and preliminarily found TikTok in breach over minors' account safety.
  • Snapchat's self-declaration approach was deemed insufficient in an investigation that began as a Dutch inquiry and was taken over at EU level.

⚠️ GOTCHA — the message regulators are sending, stated plainly: passive age gates are no longer acceptable. Emerging enforcement shows the inadequacy of age-assurance methods based on self-declaration and age estimation rather than verification. ⚠️ If your compliance plan is a "are you over 13?" checkbox, it is already behind.

And note the compounding problem: platforms operating across the EU and UK face overlapping obligations and must satisfy whichever standard is stricter on each surface.

9.3 Where it's heading

The EU Digital Identity Wallet is required to be operational by 31 December 2026, with the Commission developing an interim age-verification solution in the meantime. ⚠️ A structural proposal worth watching: shifting age verification to the operating system, so a device verifies once and passes an age signal to apps — Colorado legislators have considered exactly this. If that model wins, it changes the integration problem entirely.

[DURABLE] What to build regardless: an appeals mechanism that works, transparency reporting infrastructure (⚠️ you cannot retrofit the data collection), statements of reasons attached to enforcement actions, documented risk assessments, and age-assurance that doesn't require you to store identity documents — ⚠️ receive a token and an audit ID, not a passport scan, or you have created a much worse liability than the one you were solving.

04 同仓库更多 Skills

the-vibey-project
the-vibey-project/vibey

white-paper-writing

Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks "how should I structure this" for a long-form document.

★ 5
the-vibey-project
the-vibey-project/vibey

prose-technical-mechanics

Use when editing or writing prose at a technical/mechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.

★ 5
the-vibey-project
the-vibey-project/vibey

prose-mechanics

Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate/Jamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix "AI-sounding" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.

★ 5
the-vibey-project
the-vibey-project/vibey

narrative-structure

Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or "how should I structure this story/pitch/presentation" request.

★ 5
the-vibey-project
the-vibey-project/vibey

legal-brief-writing

Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic/neurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.

★ 5
the-vibey-project
the-vibey-project/vibey

journal-publishability-criteria

Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs/paper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.

★ 5