[Publius6961]

The domain name is translated into an IP number, and that's how the computers actually communicate.

Which is easier to block as a list on a server? IP numbers or multiple names assigned to a specific IP number?

Just wondering...

[Izzy Dunne]

If you're talking about blocking IP NUMBERS, at the ISP level, then the XXX idea adds nothing new. You can do that already.

But if people think that having their kid's computer set up to block *.xxx is going to work, I'm betting against it.

Oh, it might prevent a few accidents, like if Whitehouse.com was forced to move to Whitehouse.xxx, but that's about it.

[MediaMole]

The ISP's nameserver can easily block DNS lookup for all .XXX domains. It's simple, one entry and all the .XXX domains go away for that ISP's users. It doesn't stop everything -- or even that much, but it is something.

Sure, you can still get to the site through it's IP address, but finding the IP will take research.

Personally, I think the objection from the right is that .XXX domains legitimize online pornography. Once there is a porn domain, porn has been sanctioned as an official and accepted part of the net.

[Doohickey]

Which is easier to block as a list on a server? IP numbers or multiple names assigned to a specific IP number?

The problem is that blocking a specific IP address would not be effective. And since porn sites are often hosted by legitimate web providers, blocking ranges of IP addresses is likely to block access to sites you actually want to visit.

Plus, the management overhead would be burdensome. Better to each proper behavior, IMO.