Linked by Thom Holwerda on Wed 12th Dec 2012 22:03 UTC
Permalink for comment 545263
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-01-25
Did you even try? If you are explicit enough, and "tittyfucking" is pretty explicit, you don't need to add a qualifier at all - it works as is (assuming safeSearch is turned off).
The algorithm may not be perfect, but it is pretty good. Words that may have non-pornographic meanings (for example, "fuck" is commonly used as an expletive) are handled by default in a manner to filter out pornographic content, you have to be more specific in order to get them to return pornography
For example, "stupid fuck" filters out almost all porn images (although a few get through), "redhead fuck" doesn't - lots of porn!
Is that really so bothersome? I really think everyone has just had a knee-jerk reaction to this feature - it is actually quite logical to me, no politics involved...