Profanity Filter
- 19 Jul 2024
- 1 Minute to read
- Contributors
- Print
- PDF
Profanity Filter
- Updated on 19 Jul 2024
- 1 Minute to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Masks unwanted expressions in a given text, filtering out offensive language and inappropriate phrases.
Parameters:
name | description | default |
|---|---|---|
| Address | Address of the profanity filter service | http://core-profanity/v1/text/profanity |
| IgnoreSslErrors | ignore any certificate errors if Profanity address contains https | false |
| Language | Indicates the language of the text to be filtered | en-US |
Inputs
Events:
| name | description | known nodes that generate this event |
|---|---|---|
| * | all events containing the 'Text' field | SR Http |
Outputs
Audio:
none
Events:
| name | description |
|---|---|
| * | Re-raises any input event after masking the Text field. Adds "filtered" to Event.Data.TextAttributes |
Filtered Phrases
An Asterisk "*" appears in place of each letter filtered.
Project Structure
A minimal sample project can be built as such:
A project that utilizes several text manipulation services can be built as such:
Service Order
It is important that Profanity Filter node is used after the Normalizer and Punctuation nodes. Otherwise, the filtered asterisks will be seen as punctuation by the other services and be manipulated as such.
Supported flow types: Stream, Batch
Was this article helpful?