Ban every link and your artists, streamers and builders stop posting. Ban nothing and your server becomes a billboard. The difference has never been the link — it's who's posting it, where, and how often.
Every one of these contains a link or a plug. A keyword rule treats them identically. Tap any card to read why it landed where it did.
Left alone
Members contributing
waiting…
Sent to a mod
Your judgment, with context
waiting…
Removed
Farming your members
waiting…
Account age, message history, whether they've ever participated in a conversation that wasn't about their own project.
Your #showcase channel exists for this. Your #help channel doesn't. Same message, different answer.
Once a month reads as sharing. Three times a week in the same channel reads as a campaign, even from a good member.
Content for your community, or a pitch that would be identical in any other server? The copy-paste ones announce themselves.
Half of self-promotion isn't text at all — it's a banner with a handle painted on it, or a QR in a profile picture.
The strongest signal on the page. If your team has consistently allowed indie devs and removed sub-for-sub, that becomes the line.
Promotion also hides in display names and nicknames — a spotless message from "gxmble.win FREE $$$" is still an advert.
A spam post costs you thirty seconds. Deleting a regular's first finished project costs you that member, and quietly, the three friends who saw it happen.
Yes, and most teams do. Channel-level standards are part of the first tuning pass — #showcase and #general get different thresholds.
Allow-listed, with a note in the feed so nobody on the team wonders why that post survived.
That's the normal starting point, and the audit is usually the most useful part of onboarding. We show you what your team has actually been doing, then you decide the line deliberately.
It can't read DMs, but the behaviour that precedes a DM wave — a fresh account adding dozens of members — is visible, and it flags that.
Tell us the posts your team argues about. We tune against those first — and we onboard five servers per batch, quoted individually.
The overnight wall of garbage, and how to stop rewriting filters for it.
The training loop: every override your mods make becomes a rule you never write.
What a moderation bot has to get right in 2026 — and where the classics stop.
NSFW, gore and slurs handled the same way at 3am as at 3pm.
Why wordlists lose to one swapped character, and what reads intent instead.
Unmasking redirect chains, fake giveaways and QR drainers before members click.