21 ms·
I disagree. Setting aside the problem of global top level domains, which I think are a bad idea, tagging adult sites via domain names greatly facilitates filter
by gwright 15y ago
I disagree. Setting aside the problem of global top level domains, which I think are a bad idea, tagging adult sites via domain names greatly facilitates filtering as compared to meta tags.
Meta tags are an application level concept and so they have to be implemented at that level via browsers or HTTP proxies, or deep packet inspection.
DNS based filtering can be done more simply via network layer devices without having to look at the application level content. So DNS filters would work even if the website content was encrypted, for example.
From an administrative point of view it is much easier to control and manage network infrastructure than it is to control individual browsers or application level gateways.
- andrewvc 15y agoNot really, since nothing is guaranteed to be on .xxx. If there was a requirement that people be forced onto .xxx you'd be correct, but people are going to be doing deep inspection anyway if they actually care about blocking content.
- gwright 15y agoThe question of enforcement is an entirely different one. I was talking about the mechanism, not the legalism. This is one reason why global top level domains are a bad idea, there is no clear legal jurisdiction for them unlike country code domains. A legal framework can be built around xxx.us, for example, because it would map to an existing legal jurisdiction. The same can't be said for .xxx or meta-tags in documents served from arbitrary domains/locations.