Commentary

InformationWeek
InformationWeek  

Filtering Out Smut

The Government Accountability Office, in a recent report entitled File Sharing Programs: The Use of Peer-to-Peer Networks to Access Pornography, said Google and Yahoo search engines failed to effectively block pornographic and erotic images. The GAO, the investigative arm of Congress, conducted its tests in February, as we reported last week. Much has changed since last winter's test.
The Government Accountability Office, in a recent report entitled File Sharing Programs: The Use of Peer-to-Peer Networks to Access Pornography, said Google and Yahoo search engines failed to effectively block pornographic and erotic images. The GAO, the investigative arm of Congress, conducted its tests in February, as we reported last week. Much has changed since last winter's test.InformationWeek recently conducted a similar test. We set the search engines' filters to their strictest settings and employed search terms teens would likely use to find erotica images. Google and Yahoo returned few, if any, X-rated images. In fact, in its strictest setting and using common four-letter words and related pornographic search terms, Google wouldn't let searchers access any photos, videos, or illustrations, even those depicting innocent images.

But technology, of course, won't necessarily protect our kids from viewing porno online. These filters can be easily disabled by youngsters, many of whom are more Net savvy than their parents. The kids merely must swear they're at least 18 years old.


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links