New RFC Considers .sex TLD Dangerous 421
netcentric writes "A post on CircleID has reported about an RFC prepared by Donald E. Eastlake 3rd and Declan McCullagh, CNET News.com's Washington D.C. correspondent, analyzing proposals from various parties to mandate the use of special top level domain names (such as .sex or .xxx) or an IP address bit to flag 'adult' or 'unsafe' material or the like. The analysis explains why these ideas are dangerous and ill considered from legal, philosophical, and technical points of view. Here is the post to this report on CircleID along with some commentaries and link to the entire RFC 3675."
RTFA (Score:4, Informative)
Re:you already can (Score:1, Informative)
The new.net code is a layered service provider that gets up into your Windows IP stack and niggers things up badly. You need both Ad-aware -and- Spybot to get rid of it. They're not real domains, either. you need their crapware to view them.
Don't even RTFP, just RTFH! (Score:1, Informative)
Emphasis mine.
I guess it's too much to ask these days...
Re:Obligatory Scrubs Quote (Score:2, Informative)
Re:Lieberman (Score:2, Informative)
Let me guess... You just woke up from a coma, and you think it's still 1998? An on-line business does NOT make money from page views, they make money from customers paying for products and services. Why would you want little kids going to your porn site? Kids don't have credit cards, and MOST of them wouldn't ask their parents to order porn for them.
Actually, from a business standpoint, there are good arguments both for and against self-regulation. Hard to tell how this is gonna play out; most likely, nothing will get decided, and everything will just continue as before.