Inviting and bot setup

There are two ways to add the bot to your Discord server:

  1. Invite link via Dashboard
  2. Invite link from third-party Discord bot list
  3. Installing/inviting via App Directory on Discord itself



Invite and setup

Once you've invited the bot to your server head over the the dashboard using the link in your private message.


What's next?


Filtering is active

Once the bot is added to your server it will check messages and remove offending messages automatically. By default DeepSense filter is used (can learn more at Choosing which filter method to use - explained). 

Filter options

Choose how strict you want your filtering experience to be for your server using filter options in the dashboard. This allows you to tailor the experience for your specific guidelines and community.

Profanity Report

If your server is busy enough, after 7 days you can check the Profanity Report for a detailed analysis of good/bad messages. This gives you a week by week overview and sampling of the type of content that is being removed by ProfanityBlocker

Gamification system

Decide if you want the gamification system on, by default it is off. Learn more at Gamification/Civility Ranking System - FAQ

Actions/Conditions (AKA, If This Then Profanity Blockes/IFTTPB)

After logging into the Dashboard you might want to automate what to do with offenses, things like warn, kick or ban. Check IFTTPB - explained for more.




Resources

  • Page:
    Custom Model Filter - explained (ProfanityBlocker Support)

    As a user of the profanity filtering service, you interact with two main components: the request history and your custom profanity dataset. Here's how they work from your perspective:

    Request History

    Whenever you use the service to check text for profanity, the system records the details of your request. This includes:

  • Page:
    False Positive Reporting - explained (ProfanityBlocker Support)

    As a user of the profanity filtering service, you interact with two main components: the request history and your custom profanity dataset with the selected filter's base model. Refer to custom model filtering help to learn more about this.

    Here's how they work from your perspective:

    Request History

  • Page:
    Supported Languages in Models - explained (ProfanityBlocker Support)

    Our filter models (excluding DeepSense) are trained on the English language, and message submissions in other languages could potentially block those messages (a false positive). Conversely, the filter will be unable to detect toxic and inappropriate language that is not in English.

    At present, the DeepSense filter supports the following languages simultaneously:

  • Page:
    Choosing which filter method to use - explained (ProfanityBlocker Support)

    When it comes to filtering for toxic language, whether that's profanity or content most people would be offended by there's no one size fits all for everyone. Given this fact, we've taken the approach of building and tuning different types of models for different scenarios.

    Here's a breakdown of the filter methods with its use cases explained: