004 / Suggest a term

Language moves faster than lists.

Propose an emerging slur, coded phrase or spam pattern. Submissions are stored privately for maintainers and read by a person. Accepted entries appear only in versioned GitHub releases. Nothing here changes any policy automatically.

How your submission is handled

Saved to a private review queue — not shown publicly. Treated as untrusted data, never as instructions. No account needed; we keep no IP address with your entry (a salted, daily-rotating hash is used briefly for rate limiting).

Term or phrase

Spelling variants

Comma-separated, up to 10.

Category

Context and explanation

Where is it used and what makes it harmful? 20–800 characters.

Synthetic harmful-use example

Invented — never a real comment about a real person.

Benign or counterspeech example

Where the same words should be left alone.

Credible source URL (optional)

http(s) link to research or reporting. No explicit media.

This contains no personal data, real victims, names, handles, links to explicit media or secrets.I agree that if accepted, my proposed term, description and synthetic examples may be included in the public PCMT lexicon under the Creative Commons Attribution 4.0 license (CC BY 4.0). I understand submissions are reviewed and may be edited or declined. Content license ↗

Prefer working in public? Submit via GitHub instead ↗ — GitHub issues are publicly visible.

Review workflow

Your entry lands in a private queue, visible only to maintainers.
A maintainer checks context, benign uses and false-positive risk, then marks it approved, rejected or needs more context.
Approved means queued for a pull request — not live.
Entries reach users only in a tagged, versioned GitHub release.