<?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</title>
	<atom:link href="http://pervscan.com/2004/04/05/xxx/feed/" rel="self" type="application/rss+xml" />
	<link>http://pervscan.com/2004/04/05/xxx/</link>
	<description>An Index to the Sordid and Depraved</description>
	<lastBuildDate>Sun, 25 Mar 2012 06:21:31 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PornLaw</title>
		<link>http://pervscan.com/2004/04/05/xxx/comment-page-1/#comment-863</link>
		<dc:creator>PornLaw</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervscan.com/blog/?p=308#comment-863</guid>
		<description>I disagree. 

Point 1:  For the government to require that all adult content be on .xxx, it would have to prohibit adult content on all other TLDs.  That&#039;s not constitutionally permissisible.  Even if it were, what would the government do about non-US citizens who own and operate .com adult sites outside the US?  What about .uk adult sites?  As a practical matter, it&#039;s not possible to effectively segregate content in this way.   Moreover, if the government is trying to outlaw dirty pictures, we&#039;ve got bigger problems than whether the dirty pictures are at .com or .xxx.

Point 2: If it&#039;s voluntary, which it will be, this is a non-issue.  If it&#039;s not voluntary, see point 1 above.

Point 3: Who cares?  This is for the .xxx people to worry about.  If no one registers the domains, they&#039;ll go out of business.  That&#039;s not a reason to prevent them from doing it.

Point 4: This isn&#039;t even a point, it&#039;s just your speculation.  Given the number of major adult companies that support the .xxx concept, it&#039;s probably wrong.

Point 5: No one is compelled to register .xxx domain names.  If trademark owners choose to register .xxx domains defensively, that&#039;s their choice.  If they choose not to, they can still sue anyone who infringes their trademarks.

Also, this concern is not unique to .xxx, it&#039;s an issue with all new TLDs.  The .xxx people shouldn&#039;t be expected to have a perfect solution, since no one else has.

Conclusion:  Everyone presumably agrees that it would be nice if there were a way to keep Internet porn away from kids.  .xxx might help achieve that goal, or it might not.  The fact that it might not work isn&#039;t a good reason to prevent its proponents from trying it, since there&#039;s no apparent downside.  

Those who disagree with the last statement should consider: if the government wants to segregate porn, why couldn&#039;t it just do so, whether or not .xxx exists?   How does .xxx make any difference?</description>
		<content:encoded><![CDATA[<p>I disagree. </p>
<p>Point 1:  For the government to require that all adult content be on .xxx, it would have to prohibit adult content on all other TLDs.  That&#8217;s not constitutionally permissisible.  Even if it were, what would the government do about non-US citizens who own and operate .com adult sites outside the US?  What about .uk adult sites?  As a practical matter, it&#8217;s not possible to effectively segregate content in this way.   Moreover, if the government is trying to outlaw dirty pictures, we&#8217;ve got bigger problems than whether the dirty pictures are at .com or .xxx.</p>
<p>Point 2: If it&#8217;s voluntary, which it will be, this is a non-issue.  If it&#8217;s not voluntary, see point 1 above.</p>
<p>Point 3: Who cares?  This is for the .xxx people to worry about.  If no one registers the domains, they&#8217;ll go out of business.  That&#8217;s not a reason to prevent them from doing it.</p>
<p>Point 4: This isn&#8217;t even a point, it&#8217;s just your speculation.  Given the number of major adult companies that support the .xxx concept, it&#8217;s probably wrong.</p>
<p>Point 5: No one is compelled to register .xxx domain names.  If trademark owners choose to register .xxx domains defensively, that&#8217;s their choice.  If they choose not to, they can still sue anyone who infringes their trademarks.</p>
<p>Also, this concern is not unique to .xxx, it&#8217;s an issue with all new TLDs.  The .xxx people shouldn&#8217;t be expected to have a perfect solution, since no one else has.</p>
<p>Conclusion:  Everyone presumably agrees that it would be nice if there were a way to keep Internet porn away from kids.  .xxx might help achieve that goal, or it might not.  The fact that it might not work isn&#8217;t a good reason to prevent its proponents from trying it, since there&#8217;s no apparent downside.  </p>
<p>Those who disagree with the last statement should consider: if the government wants to segregate porn, why couldn&#8217;t it just do so, whether or not .xxx exists?   How does .xxx make any difference?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wegfewrg</title>
		<link>http://pervscan.com/2004/04/05/xxx/comment-page-1/#comment-864</link>
		<dc:creator>wegfewrg</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervscan.com/blog/?p=308#comment-864</guid>
		<description>OK.
</description>
		<content:encoded><![CDATA[<p>OK.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

