Content moderation overview
Nexconn supports content moderation for instant messaging.
- The IM service includes a built-in profanity filter mechanism. Note that the profanity filter is a basic protection mechanism limited to text content (50 profanity words by default) and cannot replace a professional content moderation service.
- To implement your own moderation or integrate a third-party moderation service, use pre-messaging webhooks.
Profanity filter
The client SDK does not provide management APIs for this feature, only a callback API to notify the sender when a message is blocked. See Profanity filter callback.
The profanity filter is a basic protection mechanism that detects and filters profanity words in text message content. For messages containing profanity words, you can choose to block the message entirely (not delivered to the recipient) or replace the profanity words according to specified rules before delivery.
Supported languages: Chinese, English, Japanese, German, Russian, Korean, and Arabic.
Manage profanity words for your App Key's development or production environment:
| Action | Client API | Server API |
|---|---|---|
| Add profanity words (with replacement content) | Not available | Add profanity words |
| Remove a profanity word | Not available | Remove profanity word |
| Batch remove profanity words | Not available | Batch remove profanity words |
| List profanity words (with replacement content) | Not available | List profanity words |
Default behavior
- Up to 50 profanity words by default.
- Applies only to messages sent from the client SDK by default.
- Detects profanity words only in the built-in text message type (
RC:TxtMsg) by default. Supports Direct, Group, Open, and Community channels. In Community channels, edited text message content is also subject to profanity word detection and filtering.
Configuration options
- To apply profanity filtering to messages sent via the Server API, enable the Moderate messages sent by server API toggle in the Console under Chat > Chat settings > Security & Moderation.
Pre-messaging webhooks
To integrate your own moderation system or a third-party content moderation service, subscribe to the *:pre_messaging webhook events in the Console under Chat > Webhooks.
Pre-messaging webhooks provide a message filtering mechanism. You can route messages to your designated server based on sender ID, recipient ID, message type, channel type, and other parameters. In Community channels, message edits and message expansion updates can also be routed to your server.
After messages are routed to your server, your moderation system (or a third-party system) can review the content. The Nexconn server determines whether to deliver the message, replace content, or block the message based on your server's response.
For details on creating routing rules and webhook parameters, see the pre-messaging webhooks documentation.