GLINR Studio LogoTypeWeaver

Troubleshooting & FAQ

Common issues and solutions for profanity detection problems

Edit on GitHub

Comprehensive troubleshooting guide for common profanity detection issues. Find solutions to false positives, performance problems, missing matches, and configuration challenges with detailed explanations and code examples.

Most profanity detection issues stem from configuration mismatches or misunderstanding of how context-aware filtering and word boundaries work. This guide addresses the most common problems developers encounter.

Common Issues & Solutions

Quick Diagnosis Tool

Use this checklist to quickly identify common issues:

False Positives Checklist

  • Is wordBoundaries: true enabled? (Prevents substring matches)
  • Is enableContextAware: true configured? (Reduces context-based false positives)
  • Are you using domain-specific whitelists? (Gaming, technical terms)
  • Is confidenceThreshold set appropriately? (0.7-0.8 recommended)

Missing Matches Checklist

  • Is allowObfuscatedMatch: true for disguised profanity?
  • Are the correct languages configured?
  • Is wordBoundaries: false for embedded profanity?
  • Is fuzzyTolerance set low enough? (0.6-0.8)
  • Is context analysis overriding valid detections?

Performance Issues Checklist

  • Are you checking too many languages?
  • Is caching enabled for repeated content?
  • Are you reusing Filter instances?
  • Is context analysis disabled for simple use cases?

Configuration Issues Checklist

  • Are parameter names correct? (camelCase JS, snake_case Python)
  • Are value types correct? (arrays, numbers, booleans)
  • Are ranges valid? (0.0-1.0 for thresholds)
  • Are language codes correct?

What's Next?


Still having issues? Check the GitHub Issues for additional troubleshooting help, or create a new issue with your specific configuration and problem description.