Shout Families to ICANN — “No Porn!”
Anti-porn group mobilized against .xxx.
If ICANN is supposed to include the thoughts of the greater internet community, it is certainly getting its wish.
Focus on the Family Some advocacy group — whether it be a religious right organization, parents organization, or someone else — has lit a fire under dozens of people to submit comments to ICANN regarding .xxx.
The comment period for the procedural issues around reconsidering ICM Registry’s .xxx application opened yesterday, and by now there are over 50 comments. Subject lines include:
“Re: against porn web domains”
“PLEASE STOP EXPOSING OUR CHILDREN TO PORN!!”
“.XXX Comments READ THIS”
“No on pornography!! ”
“Are You Crazy”
From reading the comments, I don’t think most people understand the issue. Here’s one comment:
I am writing to encourage those who are involved in considering making a xxx domain to please think regarding the devastating affects of porn on families and individuals. I have seen porn and the addiction that some people develop to it destroy families and relationships. Creating an xxx domain will not help protect people, but will make a smooth path for even more hurt and destruction. Think regarding the hurt and the pain and then think regarding your place in possibly allowing more.
and
WE WISH THAT OUR CHILDREN WON BE EXPOSES TO SUCH NASTY HURTFUL THING ” PORNOGRAPHY’
and
Just want you to know, that pornography has caused lots of problems in our marriage. If that’s not your intention, please do not create more problem by trying to create this dot xxx thing.
May God bless you with wisdom in making such notable decision.
Apparently God is getting involved with ICANN decisions these days. That ought to certainly speed things up.
OK, I get it. You’re opposed to porn. But creating a .xxx domain name isn’t going to result in more porn on the web. And your internet filters can easily block this porn — unlike what exists on other top level domain names.
Perhaps my favorite comment is the one that asks ICANN to “go with its initial gut feeling”, which the author states was to deny .xxx. Actually, its initial decision was to approve .xxx. Only later did it backtrack, which is why ICANN is in this mess with ICM to begin with.
