Profanity filter of tomorrow
Announcing the Profanity Filter Of Tomorrow(PFOT) pronounce P-foot.
This is a web service call that will accept a posted text field and will return the text with the curses replaced or marked. Curses can include but not limited to obscenity, indecency and profanity. The service will be provided for one or many languages. Other services like spelling and grammar checking can also be added to the webservice call.
The service will accept and return different formatted responses including but not limited to Hyper Text Markup Language (HTML), JavaScript Object Notation (JSON), and Extensible Markup Language (XML).
Curse word dictionaries will be updated periodically by an aggregation of different sources including but not limited to humans and internet sources.
Why?
Although it is easy to program a simple white list to filter out profanity. There are a few problems with coding a white list. The first problem is the maintaining the list of words. Kids keep creating new ways to express those same old works. New slang, alternate spellings and fun elite(l33t) speak. A second problem is customization. I might want to filter some fields more or less strict or I might want to replace the bad words will fun silly words. I might want to replace the curses with curses from a different language. A third is foreign languages. Sure start filtering English and everyone will start cursing in French.
Stay tuned...
This is a web service call that will accept a posted text field and will return the text with the curses replaced or marked. Curses can include but not limited to obscenity, indecency and profanity. The service will be provided for one or many languages. Other services like spelling and grammar checking can also be added to the webservice call.
The service will accept and return different formatted responses including but not limited to Hyper Text Markup Language (HTML), JavaScript Object Notation (JSON), and Extensible Markup Language (XML).
Curse word dictionaries will be updated periodically by an aggregation of different sources including but not limited to humans and internet sources.
Why?
Although it is easy to program a simple white list to filter out profanity. There are a few problems with coding a white list. The first problem is the maintaining the list of words. Kids keep creating new ways to express those same old works. New slang, alternate spellings and fun elite(l33t) speak. A second problem is customization. I might want to filter some fields more or less strict or I might want to replace the bad words will fun silly words. I might want to replace the curses with curses from a different language. A third is foreign languages. Sure start filtering English and everyone will start cursing in French.
Stay tuned...
