Say That Again

Say That Again

by Mike Masnick




A Separate Domain For Porn? How Original!

from the so-damn-original dept

It's only been discussed for years, and ICANN has been considering it for about a year, but Broadband Reports has discovered that some Maryland lawmaker thinks he came up with the idea for a porn-only top level domain. He's so thrilled with himself that he says people keep telling him: "What took so long? Why didn't anybody think of this before?" Um... they have. And, there's been plenty of discussions about it. Including all of the trouble it would cause, such as how, exactly, do you define porn? Do you force all porn sites to go to this new domain? If so, how do you deal with the ones who have "prime real estate" now and want the equivalent in a porn-only TLD? What about the borderline cases such as artistic porn... or, as they like to say these days, "erotica"? So, while it's an intriguing idea, it's not particularly new and it's not quite as simple as this guy makes it out to be.

11 Comments | Leave a Comment..

 
 

Reader Comments

(Flattened / Threaded)

    Jan 21st, 2005 @ 1:15pm
  • Yifferific

    by dorpus

    Politicians and their confurrences?

    (reply to this comment) (link to this comment)

  • Jan 21st, 2005 @ 1:24pm
  • But seriously

    by dorpus

    Politicians help to put techie issues into the mainstream. Until then, it's just a bunch of nerd lobbyists gabbing about strange topics.

    (reply to this comment) (link to this comment)

  • Jan 21st, 2005 @ 1:34pm
  • once again

    by justin

    you sounds great on paper will never happen. just to many porn sites.(thank god) :)

    (reply to this comment) (link to this comment)

  • Jan 21st, 2005 @ 1:54pm
  • reminds me of the RFC...

    by nonuser

    that proposed adding an attack flag to IP headers to help firewalls identify malicious packets.

    (reply to this comment) (link to this comment)

  • Jan 21st, 2005 @ 2:33pm
  • A Separate Domain For Porn? How Original!

    by Proud coward

    If there was a specific domain, don't be surprised if suddenly a strong need arises by certain "concerned elements" to block those sites from being allowed into their fine and decent communities.

    (reply to this comment) (link to this comment)

  • Jan 21st, 2005 @ 2:57pm
  • better solution

    by Anonymous Coward

    create a .kids domain(which already exists?) and force all kid-friendly content to those domain.

    (reply to this comment) (link to this comment)

    • Jan 21st, 2005 @ 4:17pm
    • .sex not only .kids

      What I think might make sense is to have a .sex and a .kids, but to allow sites to use them as they wanted.
      The key would be to make it DESIRABLE for sites to "self classify" themselves, e.g.
      .kids -- Sites that honored reasonable strong non-ponography standards, though I can't define it. The advntage would be that this domain would not be filtered out, but porn sites might have to post a bond to ensure that they did not violate the standards.
      .sex -- Sites that would not be held to local pornograpy standards (perhaps not to any) thus the GOVERNMANT would give up their right to censor them, even through the court, but that could be filtered out by isp's based on a specific request from their customer. These sites would have some protection against legal action, but would have to accept simple filtering if an individual wants to so filter.

      (reply to this comment) (link to this comment)

    Jan 21st, 2005 @ 6:49pm
  • It's Not That Difficult, Either

    No, it's not that simple, but it's not that difficult, either — once you define what goes on that domain.

    Here's my plan, slightly revised from my previous suggestion. Any adult site would automatically get the corresponding domain name in the .sex or .xxx TLD. If multiple sites had the same second-level domain name, the first registered would get that name in the new TLD; the others would have to come up with new names.

    Sites in the old TLDs would have a fixed period of time (6 months?) where they could redirect traffic from the old URL to the new URL, after which the old domain names would be invalidated (with pro-rated credit given for any remaining time).

    Of course, unless ICANN formalized those rules, they would only apply in the U.S.; if ICANN made it "law", perhaps it could apply worldwide. Regardless, there would have to be a problem resolution center for non-complying domains, similar to how domain squatting disputes are resolved.

    (reply to this comment) (link to this comment)

    • Jan 22nd, 2005 @ 7:45am
    • Re: It's Not That Difficult, Either

      by nonuser

      Except I suspect most adult sites would want to keep their .com or .net names, few would want a .sex name which would be shut out by corporate firewalls.
      And the EFF would probably be in their corner with their legal staff. One point is, you don't want legislators holding press conferences and hearings on whether this or that web site ought to be moved to the .sex domain.

      (reply to this comment) (link to this comment)

    Jan 22nd, 2005 @ 3:29am
  • No Subject Given

    by Anonymous Coward

    What is the matter with instituting this as a stop-gap solution? Not everything is fool proof, but if we waited for the fool proof solution nothing would be done.

    You don't like filters, you don't like porn TLD's, you don't like any kind of censorship or restrictions.... what do you like? What do you propose?

    (reply to this comment) (link to this comment)

  • Jan 23rd, 2005 @ 3:59am
  • Let us not forget

    by kevin

    That there are MANY with power and money that would LOVE nothing better than to tell you what to watch/think/read/believe who would JUMP at the chance for this.How long after .sex goes online before some relgious watchdog group sues your ISP saying .sex shouldn't be allowed in your area?The powerful have enough control over our lives.Filters at home will protect children.This "for the kids" is ALWAYS used by people that want to treat YOU like a child.

    (reply to this comment) (link to this comment)

Add Your Comment

Have a Techdirt Account? Sign in now.
Get Techdirt’s Daily Email
Plain Text HTML
Save me a cookie
  • Plain Text: A CRLF will be replaced by break <br> tag, all other allowable HTML is intact
  • HTML: No formatting of any kind is done without explicitly being written in
  • Allowed HTML Tags: <b> <i> <p> <a> <em> <br> <strong> <blockquote> <hr> <tt>
Close
Have a Techdirt Account? Sign in now.
Get Techdirt’s Daily Email
Plain Text HTML Save me a cookie

Search Techdirt
And now, a word from our Sponsors..



Subscribe to Techdirt's Daily Email Newsletter

Techdirt's Daily Email Newsletter

Related Stories
Close
E-mail It