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.
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.
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).
> It's impossible to filter it all
And?
.xxx won't change that. At all.
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.
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.
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 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.
There already is voluntary compliance amongst the the big producers, as well as the smaller ones. There is no incentive to attract children.
These sites have already a vested interest in their current domains. Do you realize the cost involved with moving domains at the scale you are discussing? For what? To do what's already possible and being done?
I'd be more worried about sites that you wouldn't think to place in .xxx and yet are in many ways worse (looking at you, reddit!)