Proposal for porn domain revived


Recommended Posts

http://news.bbc.co.uk/1/hi/technology/6240725.stm

Source: BBC News

Proposal for porn domain revived

Plans to create an internet domain for pornographic websites have been resurrected.

The proposal for the .xxx domain was rejected in May 2006 by the overseer of the net's addressing system over fears about how it would be run.

But the proposal has won approval following promises by the domain's backer to actively police any site that signs up to use the .xxx suffix.

The plan has come under fire from pornographers and politicians.

History lesson

The idea of creating a net domain for pornography was first floated in 2001 and attempts to set up the system have had a troubled history.

The proposal was given approval in June 2005 by the Internet Corporation for Assigned Names and Numbers (Icann) which oversees the net's addressing system.

Final approval was scheduled to take place in December 2005 but this was delayed until May 2006 when the proposal was abruptly dropped.

At the time Icann boss Paul Twomey said the decision was not "politically motivated" and now documents posted on the Icann site show that the decision was taken over worries about how sites signing up to use .xxx would be policed.

As a result, ICM Registry - the backer of the .xxx scheme - has given pledges that it will ensure sites signing up do not hit users with spam or spyware. Sites will also have to use a tagging system that accurately labels their content.

ICM must also put in place systems that stop children seeing the sites and ensure no .xxx sites are used to promote child pornography or any "practices that appeal to paedophiles or suggest the presence of child pornography on the site".

Icann has now invited the public to comment on the revised .xxx agreement. Those interested have until 5 February to comment.

In the past, plans for the .xxx domain have come under fire from conservative groups, politicians and even pornographers. Some operators of adult sites fear that adopting the .xxx domain would make it easier for such sites to be blocked en masse.

Critics have also noted that use of the .xxx domain is entirely voluntary and some suspect that few sites would sign up to use the suffix.

If final approval is won it is not yet clear when the domain will start operating.

Link to comment
https://www.neowin.net/forum/topic/528335-proposal-for-porn-domain-revived/
Share on other sites

its a strange one this. I've always thought its silly. for instance...

a kid wants to look at some porn, he/she has to use some imagination to thing of what could be a site name. sara.com isnt going to be porn.

But if only porn can use the .xxx they can just type anything and no doubt it will be porn!

All they need to know is the xxx bit, not the rude words...

does that make sense?

its a strange one this. I've always thought its silly. for instance...

a kid wants to look at some porn, he/she has to use some imagination to thing of what could be a site name. sara.com isnt going to be porn.

But if only porn can use the .xxx they can just type anything and no doubt it will be porn!

All they need to know is the xxx bit, not the rude words...

does that make sense?

I think the idea though is that the family filter that comes with ISP's just block all .xxx domains, however I see you point, if the family does not apply the filter the kid knows where to go straight away.

its a strange one this. I've always thought its silly. for instance...

a kid wants to look at some porn, he/she has to use some imagination to thing of what could be a site name. sara.com isnt going to be porn.

But if only porn can use the .xxx they can just type anything and no doubt it will be porn!

All they need to know is the xxx bit, not the rude words...

does that make sense?

however, it would also be easier to block access to the domains. so it has it's good and bad points. i think they should use it.

I don't question that this sounds like a good idea. After all, setting up an ".xxx" filter would be very easy.

The problem I have is who determines what content gets ".xxx"? What laws get used to enforce this when the servers can be hosted in any country?

Some porn for .xxx would be obvious. How about artistic photo sessions that happen to have some nude content? Soft-core porn? Overly provocative swimwear or underwear? (I can't probably post an example link to a current Aussie provider with some partially see-through swimwear). Perhaps pictures on family websites of new baby's birth or first bath?

The biggest problem with .xxx is that there is no cut-and-dried definition of "porn" and "not porn". Add in the lack of global enforcability/laws...

This is pointless.

I don't question that this sounds like a good idea. After all, setting up an ".xxx" filter would be very easy.

The problem I have is who determines what content gets ".xxx"? What laws get used to enforce this when the servers can be hosted in any country?

Some porn for .xxx would be obvious. How about artistic photo sessions that happen to have some nude content? Soft-core porn? Overly provocative swimwear or underwear? (I can't probably post an example link to a current Aussie provider with some partially see-through swimwear). Perhaps pictures on family websites of new baby's birth or first bath?

The biggest problem with .xxx is that there is no cut-and-dried definition of "porn" and "not porn". Add in the lack of global enforcability/laws...

This is pointless.

I agree with you Mark. It sounds like an awesome idea, but to be able to actually enforce this you'd need the corporation of other countries, which isn't going to happen. And on top of that, who would be in charge of deciding what is porn and what isn't. The Victoria's Secret website shows women wearing some pretty skimpy clothing, could that be considered porn? I think to some it might be. My point is, where does the government draw the line. And what about educational purposes, personally I'm not sure if I agree that what's on Wikipedia is for educational purposes. Maybe it was uploaded with innocent purposes, but that doesn't mean it is used for innocent purposes. So could you consider that porn? Again, some might.

A nice thought, but this is pointless and a waist of time.

I agree with you Mark. It sounds like an awesome idea, but to be able to actually enforce this you'd need the corporation of other countries, which isn't going to happen. And on top of that, who would be in charge of deciding what is porn and what isn't. The Victoria's Secret website shows women wearing some pretty skimpy clothing, could that be considered porn? I think to some it might be. My point is, where does the government draw the line. And what about educational purposes, personally I'm not sure if I agree that what's on Wikipedia is for educational purposes. Maybe it was uploaded with innocent purposes, but that doesn't mean it is used for innocent purposes. So could you consider that porn? Again, some might.

A nice thought, but this is pointless and a waist of time.

The people who will 'police' the .xxx will surely have the authority to revoke or blackhole the domain name at any times and will set the exact guidelines on what is an isn't considered appropriate for the domain.

The people who will 'police' the .xxx will surely have the authority to revoke or blackhole the domain name at any times and will set the exact guidelines on what is an isn't considered appropriate for the domain.
Which will push that site to find a .com. or .hk, or .whatever.

Not a solution.

No legal authority plus no agreed-upon definition equals dismal failure.

I agree with markjensen and Hurmoth. .xxx isn't a solution. And there was a time when I thought this would be a good idea. I have changed my mind. Set aside the examples they have about other countries not cooperating and defining porn. What about Newgroups? P2P so on. .xxx will do NOT stop online porn. It may change the way it's done, somewhat, but that's about it.

its a strange one this. I've always thought its silly. for instance...

a kid wants to look at some porn, he/she has to use some imagination to thing of what could be a site name. sara.com isnt going to be porn.

But if only porn can use the .xxx they can just type anything and no doubt it will be porn!

All they need to know is the xxx bit, not the rude words...

does that make sense?

A kid can just type 'porn' into google so it doesn't matter what the domain name is!

Having a .xxx for adult sites makes sense, it makes it easier for parents/schools to block inappropriate content. It's not to stop online porn, it is there to help make it harder for kids to get their hands on it. It would be nice to think that the co-operative/legal porn sites will move to .xxx and the ones left are either dodgy or just unco-operative.

In most countries pornography is a legitimate commercial/business venture, thus, the natural attribution to .com and .biz

If theoretically they could move everything to .xxx , wouldn't we expect that the companies could charge the governments, etc for compensations?

its not a solid solution, but i think it would help...if enforced.

if it was enforced that u couldn't have ANY material on a website that could be considered pornagraphic without having a .xxx

etc....

then parents/schools/work places/library's all those places could just block that domain extension.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Fastfetch 2.64 released bringing new logos and other improvements by David Uzondu Fastfetch, the popular command-line system information tool that developers created as a fast alternative to the classic Neofetch utility, has updated its codebase to version 2.64, bringing experimental scripting power, streamlined compilation options, a smarter logo renderer, and Codec module support. As noted earlier, Fastfetch can now detect hardware-accelerated video codecs across Windows, macOS, Linux, and Android through this new Codec module. On Linux and BSD, the utility uses VA-API by default, with a fallback to VDPAU on Nvidia hardware if compiled with libva and libvdpau. Windows users get D3D12VA on Windows 11 or D3D11VA with Media Foundation Transforms on older systems, while macOS relies on VideoToolbox and Android utilizes AMediaCodec. You can manually toggle Vulkan Video via the config file, and the program will report both encoders and decoders unless configured otherwise. Logo support for Quasar, Origami, Origami_small, NixOS2, and BerserkArch also landed in this release. BerserkArch, if you have never heard of it, is a specialized Arch Linux derivative that targets security researchers and power users. This distro comes with an offensive security tool manager, simply called berserk, which allows users to install complex hacking toolkits with single terminal commands. Moving on, Fastfetch now has experimental scripting options for custom formats using Lua or QuickJS. The Lua integration supports versions 5.3 through 5.5, sharing a single interpreter instance across all modules so you can store variables globally. T Alternatively, if you prefer JavaScript, you can use QuickJS-ng version 0.15.0 or newer to evaluate your custom formats with the qjs: prefix. Other changes that version 2.64 brings include native CMake compilation flags to disable specific modules to shrink the final binary size. Users can delete unwanted ASCII logo files directly from the source directory before building to save additional space. The format engine now boasts ANSI-escape awareness, meaning you can center text with the new vertical bar specifier without breaking colored outputs. Haiku users receive preliminary support for boot manager, window manager theme, screen brightness, and other basic properties. Finally, the Linux edition now extracts desktop wallpaper and theme details from the modern COSMIC desktop environment.
    • That's a good number until the game you want to play is not in that list. 
    • So, the logo means No ducking AI?
    • For sure, humanity us highly unlikely to survive the helium flash. Even if we have colonized moons in the outer planets by then, that is such a monumental change in heat output, coupled with the destruction of Earth, it's unlikely we could be fully prepared for changes of that scale.
  • Recent Achievements

    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      PsYcHoKiLLa
      240
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      70
    5. 5
      Michael Scrip
      59
  • Tell a friend

    Love Neowin? Tell a friend!