Slashdot Mirror
Why the .XXX Domain is a Bad Idea That Won't Die
Reader tqft tipped us to an opinion piece on the UK site The Guardian, which lays out the reasons why article writer Seth Finkelstein feels the .XXX domain is a terrible idea. You may recall that last year (being an election year and all), the concept of a triple-X ghetto was revived, considered, and then quashed all in the space of a few months. We also recently discussed the fact that the idea just won't die, as the company ICM Registry pushes ICANN to allow them to pass out the names by Summer. Finkelstein primarily argues that the new domain is a bad idea from a business point of view. Ignoring for a moment the issue that much of this content is already labeled, he sees this as primarily a means for ICM Registry to gain a monopoly on what is sure to be a hot-selling product. Speculators, pornographers, and above-board companies will all jump on the namespace in an effort to ensure that their domain is represented ... or not, as the case may be. Where do you fall on this issue? Would a .XXX domain be helpful for parents, or just a political salve/moneymaking scam?
A) makes porn easier to find
B) Does not solve the problem of being able to filter it with parental control software because nobody is going to shut down the porn.com's.
The porn sites have a right to exist, who are we to force them over to .xxx domains? Forcing them all to register with some central DB so they can be black listed would also be impossible becasue there is no realistic way to keep the DB updated.
My solution for addressing the filtering software problem is very simple. We amend robots.txt to include a section for Adult content.
A simple addition on porn sites of a line like this would solve the problem.
User-agent: * Disallow: /forums/ /members/ /downloads/ /
Disallow:
Disallow:
Adult:
Sites not interested in adding the field to robots.txt are not required to by law, but many websites would be willing to accommodate something like this to assist Net Nanny etc., but would fight having to leave porn.net behind for pornforyou12341.xxx tooth and nail. On the internet your company name and your domain name are often the same. Moving them to another TLD would equate to making them shut down and start over under a new name.
This would also greatly assist Google etc. in blocking some of these sites where "safe search" is turned on thus prevent people form going to a jenny.com by mistake and finding porn.
I have made this suggestion a number of time in the past. Maybe I should look into what it would take to get it drafted into an RFC?
Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
In some countries it is considered wrong for women to lift their veils so other men can see their faces, and in some women walk around with no shits on like men. Sure there are obvious cases, but who has the final word on what is and isn't sexually explicit content? Who is going to pay to enforce these new morals and who's morals?
Do the American tax payers launch a multi billion dollar crusade to purge the internet of porn and bring our Christian morals to the internationally based Internet?
Early proposals for .xx were to mandate that all porn sites use some form of age verification (ie credit card). With all the fraud on the internet do you honestly believe entering your credit card number and personal into on every porn site you see is a good idea? What age constitutes a "minor" anyway? 18 y/o like in the US? How many people here have never seen any porn before the age of 18? How did you turn out?
To me this only sounds like a pathway for rampant fraud. I don't want to complain without offering up my own solution, so I think if anything is to be done then appending robots.txt to include a line for "Adult: /" where the webmaster of the site sees fit is a much better idea. I posted more on this suggestion here
Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
While I can't speak much about the registry part of a .xxx name, I believe that it would be useful in the long run.
.xxx name for sites that are looking for a purely adult audience. Not just porn, but maybe places like adultfriendfinder, discussions involving less pleasent ideas, and so forth.
.xxx and helping the government look better at "protecting children", the FBI and what not leans off them a little. Yes, there are filters in place for porn, but they aren't always the best- it can be hard to teach a basic filter the difference between HOT NAKED BOOBIES and a page about breast cancer. Along with blocking out content that shouldn't be, it means that content that shouldn't get through does. A .xxx domain would ensure that the filter knows what to and not to pick out. (Hell, some crappy ones might now mark this page as pornographic since I mentioned "boobies".)
.xxx, and thus bringing us into the realm of "what exactly defines porn", but if it can stay as optional as choosing a .com or .net domain, then I don't see a large downfall. I'm sure others will disagree with me, though, and reply as such. (I welcome this, as someone may talk about a point I haven't thought of.)
While porn ad sites don't care about age, regular pay-for-porn sites would probably prefer those with access to a credit card, meaning those who can likely be there legally. Basically, market the
The government could work off this, too. They allow it to pass, and encourage its adoption by the "less scrupulous businesses", and in return for them moving to a
I can understand the fear of governments forcing porn sites to move to
You're not going to sell porn to people who aren't looking for it. And a TLD makes it easier to find, how is it a bad idea again?
Tluin natha Linux xxizzuss uriu olt bwael mon'tun.
Register your company's name under one TLD, the one which your users are most familiar with. Then sue everyone who registers your trademarked name under any other TLD: The existing name registries trump the domain name system. There is no need to register under all TLDs. On the contrary, it only causes confusion for your users and can wreak havoc with your search engine ranking if you're not doing it exactly right.
.com or bust, because users rarely see something else. After all, the other TLDs are just partial duplicates of .com anyway. Even big country code TLDs often cause an unbelieving stare when the email address doesn't end in .com. The last part of the domain name isn't just a delimiter, it actually means something and can be something other than .com. It is very important that we get this message through to users. Too much mail gets misdirected to the .com domain when it should have gone to the CCTLD which belongs to the company that the user wanted to send the mail to. This has got to change, and the way is more choice, not less.
Besides, we need many more TLDs. Not dozens more. Hundreds or thousands more. Only when there are too many domains to register under all will that insanity stop. Only then will other TLDs mean something. Today it's either