Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ICANN Approves Dot-XXX Domain for Porn

pcworld.com

Post reply on HN
Print view View original

31–38 of 38 posts

Re: ICANN Approves Dot-XXX Domain for Porn

#31

Post by InclinedPlane »

unexpected wrote: post #7

Can someone explain to me how this helps the Internet ecosystem? If I were a porn site, why would I want this address? Filters, parental controls, etc. are most likely going to block the entire .xxx domain - this would limit page views. History has shown that .com is the most popular TLD - how is .xxx going to help? It seems like an attempt to drum up registrar dollars.

In theory .xxx is the perfect ghetto for adult content. Dump everything there and then it becomes so much easier to filter/block/firewall, etc. Pornographers will see this coming from a mile away and most won't bother with the .xxx tld. Moreover, none of the big porn sites of today are likely to relinquish their prized .com domains. On the whole it's a bad idea that will have little result.

Re: ICANN Approves Dot-XXX Domain for Porn

#32

Post by jasonlotito »

Groxx wrote: post #30
jasonlotito wrote: post #25

Earlier quoted context omitted.

> It's pretty hard to block these sites because you have to know the domain name/information on each one. No, you do not. There are services out there that assist in this. http://www.cybersitter.com/ http://www.netnanny.com/ http://www.cyberpatrol.com/ http://www.asacp.org/ Couple this with parental controls in Windows and Mac (I'm sure it has it), and you don't have to know each domain. > Assuming large-scale volunt…

And how about any of the infinite mirrors which aren't the big producers? And do they block RapidShare? Torrents? It's impossible to filter it all (maybe with strong A.I., but show me a porn filter that has that and I'll denounce this claim).

What nonsense are you talking about? What does Rapidshare or Torrents have to do with filtering out porn sites that would use the .xxx TLD?

> It's impossible to filter it all

And?

.xxx won't change that. At all.

Re: ICANN Approves Dot-XXX Domain for Porn

#33

Post by Groxx »

jasonlotito wrote: post #32
Groxx wrote: post #30

Earlier quoted context omitted.

And how about any of the infinite mirrors which aren't the big producers? And do they block RapidShare? Torrents? It's impossible to filter it all (maybe with strong A.I., but show me a porn filter that has that and I'll denounce this claim).

What nonsense are you talking about? What does Rapidshare or Torrents have to do with filtering out porn sites that would use the .xxx TLD? > It's impossible to filter it all And? .xxx won't change that. At all.

Rapidshare hosts a lot of porn. If you're looking to filter the internet for the purity of person X, a random link could lead them through that and to porn. Q.E.D. Similarly, torrents are not always what they're advertised to be.

And I wasn't implying it will change the filtering problem. Merely pointing out that it isn't easy, which you implied quite strongly. Schools have been struggling with it since they started (magazines behind books), and paying companies like those large amounts of money for woefully incomplete solutions.

Re: ICANN Approves Dot-XXX Domain for Porn

#35

Post by pjscott »

civild wrote: post #2

I can only imagine the kind of domain name land-grab this will invoke. Squatters will be prepping their naughty keywords database in preparation, I suspect.

I think the cheapest way to get a desirable .xxx domain would be to register a nonsensical domain like "dumptrucking.xxx" and then make it a new term for some sex act. What is "dump trucking"? I don't know, and neither does anybody else -- yet. It's brand-building writ sleazy.

Re: ICANN Approves Dot-XXX Domain for Porn

#36

Post by jasonlotito »

Groxx wrote: post #33
jasonlotito wrote: post #32

Earlier quoted context omitted.

What nonsense are you talking about? What does Rapidshare or Torrents have to do with filtering out porn sites that would use the .xxx TLD? > It's impossible to filter it all And? .xxx won't change that. At all.

Rapidshare hosts a lot of porn. If you're looking to filter the internet for the purity of person X, a random link could lead them through that and to porn. Q.E.D. Similarly, torrents are not always what they're advertised to be. And I wasn't implying it will change the filtering problem. Merely pointing out that it isn't easy, which you implied quite strongly. Schools have been struggling with it since they started…

> And I wasn't implying it will change the filtering problem. Merely pointing out that it isn't easy, which you implied quite strongly

You're taking things out of context, and putting words in my mouth.

This is a discussion of the .xxx TLD. My contention is that .xxx won't improve porn blocking precisely because of the reasons you mentioned. There are already tools that do a lot of work to block it, and .xxx isn't going to change anything. The sites that would use .xxx are already blocked.

So, a porn sites are already blocked, and will use .xxx just to have it. It won't improve blocking. At the same time, .xxx won't block sites that don't play by the rules, and sites like RapidShare or Reddit, where you can find porn.

That's what I've been saying.

Re: ICANN Approves Dot-XXX Domain for Porn

#37

Post by astine »

jasonlotito wrote: post #25
cookiecaper wrote: post #21

Earlier quoted context omitted.

It's pretty hard to block these sites because you have to know the domain name/information on each one. Assuming large-scale voluntary compliance, and I think the chances are good that all the "big" producers will move over, it's much easier to just filter the xxx domain and be done with it. Usually the idea is to keep it away from children because children will willfully look at it without understanding. That page t…

> It's pretty hard to block these sites because you have to know the domain name/information on each one. No, you do not. There are services out there that assist in this. http://www.cybersitter.com/ http://www.netnanny.com/ http://www.cyberpatrol.com/ http://www.asacp.org/ Couple this with parental controls in Windows and Mac (I'm sure it has it), and you don't have to know each domain. > Assuming large-scale volunt…

No, you do not. There are services out there that assist in this.

http://www.cybersitter.com/ http://www.netnanny.com/ http://www.cyberpatrol.com/ http://www.asacp.org/

Have you ever actually used any of these tools? They are horrible. They have a much worse cpu and network overhead than McAfee and aren't remote effective filters unless set to unreasonably restrictive settings.

Proxies working on pre-compiled blacklists and whitelists are a better solution and the new tld could only help with this. Even if only new pornographic site were ever given a "xxx" tld, then it would save the effort of having to explicitly blacklist them.

Re: ICANN Approves Dot-XXX Domain for Porn

#38

Post by cookiecaper »

jasonlotito wrote: post #25
cookiecaper wrote: post #21

Earlier quoted context omitted.

It's pretty hard to block these sites because you have to know the domain name/information on each one. Assuming large-scale voluntary compliance, and I think the chances are good that all the "big" producers will move over, it's much easier to just filter the xxx domain and be done with it. Usually the idea is to keep it away from children because children will willfully look at it without understanding. That page t…

> It's pretty hard to block these sites because you have to know the domain name/information on each one. No, you do not. There are services out there that assist in this. http://www.cybersitter.com/ http://www.netnanny.com/ http://www.cyberpatrol.com/ http://www.asacp.org/ Couple this with parental controls in Windows and Mac (I'm sure it has it), and you don't have to know each domain. > Assuming large-scale volunt…

Those services either use really crappy (many false hits both ways) and heavy heuristics to try and determine that a pornographic image was downloaded and block it before display AND/OR a known "blacklist". So while you can outlist the compilation of said blacklist, someone still has to add sites that were confirmed to contain the material. Both ways are inefficient and spotty.

I admitted in my first post that you will never rid the internet of porn or make it completely unavailable to anyone. There is always a way around. But if the filter is good enough, unless the person is really determined, they will give up before they find its cracks.

Also, filtration is great for preventing an accidental stumbling-upon and so on.

A .xxx domain just makes sense, there's no reason not to do it. If you want to look at porn, you can find new sites by trying whatever, like, wallace_naked.xxx. You can filter for hyperlinks only to other .xxx sites. If you don't want to look at porn, you just blacklist the whole TLD and a great deal more work is done for you.

Again, you're right that there will still be porn on .com. I don't think anyone believes that's going to go away. But it's just a matter of simplicity; a .xxx tld helps everyone either way, so what's the problem?

I would be opposed to mandatory enforcement of this provision, but I think most legit porn producers will switch over for the citizenship points.

Post reply on HN