<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: XXX Domain faces hard times</title>
	<atom:link href="http://tech.blorge.com/Structure:%20/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/</link>
	<description>Top Technology news</description>
	<lastBuildDate>Mon, 13 Feb 2012 20:30:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jonathan Schlaffer</title>
		<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/comment-page-1/#comment-8008</link>
		<dc:creator>Jonathan Schlaffer</dc:creator>
		<pubDate>Sat, 31 Mar 2007 21:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/#comment-8008</guid>
		<description>Let&#039;s say if... the .com, .net and .xxx exist side by side some day then you could block all .xxx sites easily.  Everything else, well that could be on the block list set manually.

I wasn&#039;t talking about a Firewall, at least not a software firewall.  It&#039;s easy to configure a hardware firewall to block said sites but let&#039;s say you are dealing with the Vista firewall.  It&#039;s not at all easy to configure and any advanced configuration must be done via wf.msc (and most parents aren&#039;t going to know that).

That&#039;s where software like K9 Webprotection steps in BUT it is easy to block a single tld (such as .xxx) which really serves no purpose (yet).  Besides any net savvy kid can bypass any kind of block you have on a system so most software based systems are ineffective themselves.

The only really effective way to block porn is to set up a router with a password and block access to the sites from the router.  Any 13 year old kid with a computer could probably bypass software based systems given enough time but if they do, it&#039;s easy enough to tell.</description>
		<content:encoded><![CDATA[<p>Let&#8217;s say if&#8230; the .com, .net and .xxx exist side by side some day then you could block all .xxx sites easily.  Everything else, well that could be on the block list set manually.</p>
<p>I wasn&#8217;t talking about a Firewall, at least not a software firewall.  It&#8217;s easy to configure a hardware firewall to block said sites but let&#8217;s say you are dealing with the Vista firewall.  It&#8217;s not at all easy to configure and any advanced configuration must be done via wf.msc (and most parents aren&#8217;t going to know that).</p>
<p>That&#8217;s where software like K9 Webprotection steps in BUT it is easy to block a single tld (such as .xxx) which really serves no purpose (yet).  Besides any net savvy kid can bypass any kind of block you have on a system so most software based systems are ineffective themselves.</p>
<p>The only really effective way to block porn is to set up a router with a password and block access to the sites from the router.  Any 13 year old kid with a computer could probably bypass software based systems given enough time but if they do, it&#8217;s easy enough to tell.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Coppens</title>
		<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/comment-page-1/#comment-8007</link>
		<dc:creator>Jan Coppens</dc:creator>
		<pubDate>Sat, 31 Mar 2007 21:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/#comment-8007</guid>
		<description>How do you configure a firewall? It&#039;s simple. You only allow what is necessary and block everything else. People should take the same approach when blocking access to adult sites. Only allow access to sites you want your children to see, block access to everything else. one way to make this easier would be to create a .kids tld.

Creating a .xxx tld and forcing adult webmasters to abandon their .com, .net etc domains would not only be illegal (and in most countries even unconstitutional), it would be a very ineffective way to block access to adult websites.</description>
		<content:encoded><![CDATA[<p>How do you configure a firewall? It&#8217;s simple. You only allow what is necessary and block everything else. People should take the same approach when blocking access to adult sites. Only allow access to sites you want your children to see, block access to everything else. one way to make this easier would be to create a .kids tld.</p>
<p>Creating a .xxx tld and forcing adult webmasters to abandon their .com, .net etc domains would not only be illegal (and in most countries even unconstitutional), it would be a very ineffective way to block access to adult websites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Schlaffer</title>
		<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/comment-page-1/#comment-8006</link>
		<dc:creator>Jonathan Schlaffer</dc:creator>
		<pubDate>Sat, 31 Mar 2007 20:40:45 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/#comment-8006</guid>
		<description>Well, at least it will be easier to block .xxx sites but as long as ICANN keeps denying it then there is nothing to worry about as long as they don&#039;t have it.</description>
		<content:encoded><![CDATA[<p>Well, at least it will be easier to block .xxx sites but as long as ICANN keeps denying it then there is nothing to worry about as long as they don&#8217;t have it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Gardner</title>
		<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/comment-page-1/#comment-7999</link>
		<dc:creator>George Gardner</dc:creator>
		<pubDate>Sat, 31 Mar 2007 19:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/#comment-7999</guid>
		<description>It would be &#039;hard&#039; to force them over to the XXX domain; on the bright side, approving the XXX domain would cause digital pornography sites to buy their XXX site as well as their .COM site. In turn, it would allow the internet to have twice as much porn.</description>
		<content:encoded><![CDATA[<p>It would be &#8216;hard&#8217; to force them over to the XXX domain; on the bright side, approving the XXX domain would cause digital pornography sites to buy their XXX site as well as their .COM site. In turn, it would allow the internet to have twice as much porn.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Schlaffer</title>
		<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/comment-page-1/#comment-7995</link>
		<dc:creator>Jonathan Schlaffer</dc:creator>
		<pubDate>Sat, 31 Mar 2007 17:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/#comment-7995</guid>
		<description>Yes, a lot of porn sites do make use of .com, .net, etc but I believe part of the idea behind this would be to force them to switch over to .xxx thus making it easier for the sites to be blocked, instead of having to block individual .com, .net and so on sites, there could be an overlying rule to block any site with the .xxx suffix.

As with all things internet, it may not be possible to enforce this across the board, since there are various laws regarding porn activity in different countries and many of them exist or are hosted outside of the US, it could be difficult (but not impossible) to enforce some of these new rules.

I honestly don&#039;t know how you would force a site to change its top level domain but it must be possible...</description>
		<content:encoded><![CDATA[<p>Yes, a lot of porn sites do make use of .com, .net, etc but I believe part of the idea behind this would be to force them to switch over to .xxx thus making it easier for the sites to be blocked, instead of having to block individual .com, .net and so on sites, there could be an overlying rule to block any site with the .xxx suffix.</p>
<p>As with all things internet, it may not be possible to enforce this across the board, since there are various laws regarding porn activity in different countries and many of them exist or are hosted outside of the US, it could be difficult (but not impossible) to enforce some of these new rules.</p>
<p>I honestly don&#8217;t know how you would force a site to change its top level domain but it must be possible&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant</title>
		<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/comment-page-1/#comment-7989</link>
		<dc:creator>Grant</dc:creator>
		<pubDate>Sat, 31 Mar 2007 16:06:21 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/#comment-7989</guid>
		<description>I&#039;d assumed that this proposal would force porn sites to change to the .xxx....</description>
		<content:encoded><![CDATA[<p>I&#8217;d assumed that this proposal would force porn sites to change to the .xxx&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Coppens</title>
		<link>http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/comment-page-1/#comment-7987</link>
		<dc:creator>Jan Coppens</dc:creator>
		<pubDate>Sat, 31 Mar 2007 15:32:54 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blorge.com/Structure:/2007/03/31/porn-xxx-domain-registry-rejected-by-icann-again/#comment-7987</guid>
		<description>Since alot of adult sites already use .com, .net etc domains, creating a .xxx tld would in no way help parents block access to adult sites. Creating a .xxx tld would only benefit 1 company: the ICM.

If you want to protect children from accessing adult content, creating a .kids tld would be alot better option.</description>
		<content:encoded><![CDATA[<p>Since alot of adult sites already use .com, .net etc domains, creating a .xxx tld would in no way help parents block access to adult sites. Creating a .xxx tld would only benefit 1 company: the ICM.</p>
<p>If you want to protect children from accessing adult content, creating a .kids tld would be alot better option.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

