Re:Google’s Official Profanity API
by snorkel on Wednesday August 17, 2011 @12:34PM
(#2895872)
What the {"response": "true"} is this {"response": "true"} thing? A {"response": "true"} cache page? Are you {"response": "true"} {"response": "true"} me?! Do you really need a {"response": "true"} JSON API to do the work of a stupid {"response": "true"} array lookup? {"response": "true"}!!!
Re:Google’s Official Profanity API
by click170 on Wednesday August 17, 2011 @06:38AM
(#2894821)
My first thought was "Oh, I wonder if that means the spellcheck on my smartphone will stop substituting 'duck' when I meant to type something more profane." But after reading the article, I guess not.
I assume that must be a requirement of some ad networks
https://github.com/mogade/badwords/blob/master/en.txt
http://search.cpan.org/~abigail/Regexp-Common-2011041701/lib...
My stepfather would be most displeased if he couldn't use his name.
see: http://www.wdyl.com/profanity?q=balls
> http://www.wdyl.com/profanity?q=tennis%20balls
> {"response": "true"}