stephenhaunts/ProfanityDetector

Issues

• Base64 text being censored

  #30 opened a year ago by mokkymiah
  0

• Improve performance

  #28 opened 2 years ago by akardon1
  0

• profanity filter is a namespace but is used like a type

  #27 opened 2 years ago by SenseiDecay
  2

• Thread Saftey?

  #23 opened 3 years ago by QuinnDamerell
  1

• CensorString fails to clean words in multi-line input

  #22 opened 3 years ago by kHackett
  1

• ContainsProfanity is case sensitive

  #20 opened 3 years ago by BrianHendrickson
  0

• Reverse Scunthorpe

  #18 opened 4 years ago by PaulRReynolds
  1

• ContainsProfanity and DetectAllProfanity mismatch

  #16 opened 4 years ago by AbhishekTripathi
  1

• Feature request: accept array or List<string> in RemoveProfanity()

  #12 opened 4 years ago by twwilliams
  3

• Profanity list entries containing '$' causing regex to fail for ContainsProfanity()

  #10 opened 4 years ago by willemaster
  1

• Adding 'scunthorpe' to allow list does not prevent it being considered a profanity

  #9 opened 4 years ago by willemaster
  2

• The reverse-Scunthorpe problem

  #7 opened 4 years ago by aaron-bond
  13

• If a profanity has a 1 on the end it isn't detected

  #6 opened 5 years ago by DavidJBerman
  5

• CensorString crashes if there is a trailing space

  #5 opened 5 years ago by DavidJBerman
  4

• Namespace being the same as the class name seems to be causing imports to not work as expected

  #3 opened 5 years ago by eloisetaylor5693
  2

• None of the XML comments show in intellisense

  #4 opened 5 years ago by eloisetaylor5693
  1

• Why .NET Standard 2.1?

  #2 opened 5 years ago by halomakes
  2

• missing item

  #1 opened 5 years ago by ryanpetrick
  2