Talk:.xxx

Initial comments
Shoudln't this be updated? .xxx is now in use. Saxsux 19:31, Jun 3, 2005 (UTC)

The article has been updated. As a matter of fact, the official .xxx domain is not in use yet, and won't be for several months at the soonest. Only New.net's hack is "in use" at this point. All of which is explained in the article, I might add. Tverbeek 20:08, 3 Jun 2005 (UTC)

The Onion scooped us. It got rejected. savidan(talk) (e@) 18:17, 3 June 2006 (UTC)

Yeah, I always thought .xxx got rejected, and WON'T be used. Dan Leveille 22:43, 29 November 2006 (UTC)


 * Click It has been rejected again, article needs to be re-wrote. Code E 13:50, 30 March 2007 (UTC)
 * Done Stoneice02 14:03, 30 March 2007 (UTC)

==.sex== Is the .xxx TLD in any way related to the .sex scandal from a few years ago? --NEMT 01:44, 25 May 2007 (UTC)

¾ —Preceding unsigned comment added by 41.235.138.151 (talk) 22:41, 5 May 2008 (UTC) anup

4:08 AM 4/15/2012 Presently it appears that .xxx cost an enormous amount of money. On Godaddy it's $99.99 a year, while .com is $9.99. Discussion of impact should exist, but a quick google offered nothing. Obviously no small-time pornographer will pony up an extra $90.

May I suggest a screenshot of cnn.xxx which has a black background and the text "This domain has been reserved from registration. Copyright 2011 ICM Registry LLC"

Additionally, note that cryptome.xxx is an example of what is likely a "protest-type" use, likely to become more common as people believing filtering/censorship of access shouldn't be easy move their journalist-type sites to .xxx — Preceding unsigned comment added by 75.88.15.52 (talk) 04:13, 15 April 2012 (UTC)

Approved, finally
According to the BBC today .xxx will finally happen: http://news.bbc.co.uk/go/rss/-/1/hi/technology/10412765.stm Robirrelevant (talk) 11:29, 25 June 2010 (UTC)
 * It's been at that point before. It hasn't happened until it has happened. bd2412  T 16:22, 25 June 2010 (UTC)


 * As a board member of ICANN, I won't touch this article, but the actual resolution that the Board adopted is here. I think the New York Times describes it correctly as saying that the proposal has "moved forward". --Alvestrand (talk) 21:50, 27 June 2010 (UTC)


 * I have adjusted the copy appropriately. Those 'approval' stories certainly were premature! Wwwhatsup (talk) 08:13, 21 March 2011 (UTC)

Irrelevant opinions
I think the whole idea of a separate .xxx domain is very risky. It would be easier for governments to ban the domain entirely. It's opening Pandora's box. —Preceding unsigned comment added by 182.239.145.211 (talk) 02:00, 30 June 2010 (UTC) The article should talk more about the risks involved with introducing a .xxx domain.


 * You don't specify what risks you are referring to. If you can find reliable sources documenting those that have been suggested by informed commentators then by all means they should go in the article. "It would be easier for governments to ban the domain entirely." Well, this is effectively the situation at present, given that .xxx does not exist at the time of writing and has not existed in the past. I'm not sure what you mean by "easier" and it's not clear that you fully understand that process of TLD approval or the implications of introducing .xxx. It need not, for example, increase the amount of pornographic content on the internet if that's what you're concerned about (that'll happen anyway!). The more pressing 'risks' are likely to be along the lines of ghettoising a part of the net, where we might end up with ISPs carrying everything but "xxx" sites or governments blocking the domain ("who legitimately wants access to that stuff?", they'll say), resulting in further breakdown of network neutrality and the landscape of the internet appearing differently depending on who provides your connection. This is what occurs to me when I consider the idea of this domain but, as I said, everything in Wikipedia needs to be documented elsewhere to meet the standard for inclusion. 82.32.186.24 (talk) 21:37, 21 March 2011 (UTC)
 * Sorry, 182... If by "ban" you're referring to governments blocking connections to the domain (rather than preventing it coming into being) then I misunderstood you and we're coming at this from the same perspective I think! The bit about including information on risks with reference to reliable sources still stands of course. 82.32.186.24 (talk) 21:41, 21 March 2011 (UTC)

considered essential
Having just read 2004's RFC 3675: .sex Considered Dangerous, I'm firmly of the opinion that the notable concerns raised there about the merits and feasibility of .sex, which has since morphed into .xxx, need to be outlined in this article. I say "notable" because RFCs are issued by people who know what they're talking about when it comes to the plumbing of the internet, and are not coming at this debate from a simplistic and irrelevant "is porn bad?" perspective as seen in some press coverage. I don't have the technical understanding to incorporate the RFC into the article in summary form without the possibility of misrepresenting it, but I'm sure there are many Wikipedia editors who could do the needful. Also, we need a redirect from .sex to this article, since the issues someone looking it up needs to hear about are the same: it is essentially the same proposal under a different name. 82.32.186.24 (talk) 12:35, 29 March 2011 (UTC)


 * It's sometimes s/who know/who are supposed to know/, but this informational RFC was written by an expert in the field. It says that using a TLD to tag content won't work as expected -- if you'd expect say all "museum" topics in .museum, and vice versa, or all German content in .at/.ch/.de, and vice versa.  The ICANN folks were certainly aware of this RFC, and have no unrealistic expectations for .xxx.  The folks trying to get this TLD might have "too optimistic" expectations for their business, but followed the ICANN rules incl. considerable fees.  You could say the rules were wrong to start with, but you'd have a hard time to justify this opinion solely based on this RFC. –89.204.153.230 (talk) 20:25, 9 July 2011 (UTC)


 * (Same unregistered user as above) BTW, if you expect that web pages on servers with a domain in the .mobi TLD are supposed to work on smartphones, and if that works for you (I can't judge it), then this would constitute a counter-example for . –89.204.137.163 (talk) 07:08, 16 July 2011 (UTC)

Missing info the social conservative side of the debate over the .xxx domain
Shouldn't the article include the arguments over the creation of the domain including opposition from social conservatives and anti-porn feminist as well as from governments such as the Obama administration. Also missing is the the response from certain governments over it's creation such as Indian promising to block the .xxx domain country-wide. --Cab88 (talk) 07:01, 6 April 2011 (UTC)


 * I do believe the 'Background' section - essentially a synthesis of arguments pro and con - could be improved. There were arguments against not only from social conservatives, but also progressives fearing censorship implications. But it should be kept brief, and well reffed. If you want to start a 'Reactions' section with the Indian government response, I think that would be quite acceptable. Wwwhatsup (talk) 14:27, 6 April 2011 (UTC)

Categorisation
I see this page is categorised only in the porn categories, not in any technology or Internet categories. I'm not very familiar with how categorisation works on Wikipedia, but surely an article about a gTLD should have some computing categories applied? TRiG (talk) 18:09, 27 June 2011 (UTC)


 * It's categorized as a Sponsored Top Level Domain, that should be sufficient. I've removed "proposed" as it's beyond that stage. Wwwhatsup (talk) 06:36, 28 June 2011 (UTC)

Squatting?
Is it worth having a section on "preventive domain squatting", whereby addresses like "vatican.xxx" are purchased specifically to present them being misused? DS (talk) 13:51, 19 May 2012 (UTC)
 * If we have a good source treating this as a wider issue (rather than the single vatican thing I know of); why not! L.tak (talk) 14:02, 19 May 2012 (UTC)

Initial comments
Shoudln't this be updated? .xxx is now in use. Saxsux 19:31, Jun 3, 2005 (UTC)

The article has been updated. As a matter of fact, the official .xxx domain is not in use yet, and won't be for several months at the soonest. Only New.net's hack is "in use" at this point. All of which is explained in the article, I might add. Tverbeek 20:08, 3 Jun 2005 (UTC)

The Onion scooped us. It got rejected. savidan(talk) (e@) 18:17, 3 June 2006 (UTC)

Yeah, I always thought .xxx got rejected, and WON'T be used. Dan Leveille 22:43, 29 November 2006 (UTC)


 * Click It has been rejected again, article needs to be re-wrote. Code E 13:50, 30 March 2007 (UTC)
 * Done Stoneice02 14:03, 30 March 2007 (UTC)

==.sex== Is the .xxx TLD in any way related to the .sex scandal from a few years ago? --NEMT 01:44, 25 May 2007 (UTC)

¾ —Preceding unsigned comment added by 41.235.138.151 (talk) 22:41, 5 May 2008 (UTC) anup

4:08 AM 4/15/2012 Presently it appears that .xxx cost an enormous amount of money. On Godaddy it's $99.99 a year, while .com is $9.99. Discussion of impact should exist, but a quick google offered nothing. Obviously no small-time pornographer will pony up an extra $90.

May I suggest a screenshot of cnn.xxx which has a black background and the text "This domain has been reserved from registration. Copyright 2011 ICM Registry LLC"

Additionally, note that cryptome.xxx is an example of what is likely a "protest-type" use, likely to become more common as people believing filtering/censorship of access shouldn't be easy move their journalist-type sites to .xxx — Preceding unsigned comment added by 75.88.15.52 (talk) 04:13, 15 April 2012 (UTC)

Approved, finally
According to the BBC today .xxx will finally happen: http://news.bbc.co.uk/go/rss/-/1/hi/technology/10412765.stm Robirrelevant (talk) 11:29, 25 June 2010 (UTC)
 * It's been at that point before. It hasn't happened until it has happened. bd2412  T 16:22, 25 June 2010 (UTC)


 * As a board member of ICANN, I won't touch this article, but the actual resolution that the Board adopted is here. I think the New York Times describes it correctly as saying that the proposal has "moved forward". --Alvestrand (talk) 21:50, 27 June 2010 (UTC)


 * I have adjusted the copy appropriately. Those 'approval' stories certainly were premature! Wwwhatsup (talk) 08:13, 21 March 2011 (UTC)

Irrelevant opinions
I think the whole idea of a separate .xxx domain is very risky. It would be easier for governments to ban the domain entirely. It's opening Pandora's box. —Preceding unsigned comment added by 182.239.145.211 (talk) 02:00, 30 June 2010 (UTC) The article should talk more about the risks involved with introducing a .xxx domain.


 * You don't specify what risks you are referring to. If you can find reliable sources documenting those that have been suggested by informed commentators then by all means they should go in the article. "It would be easier for governments to ban the domain entirely." Well, this is effectively the situation at present, given that .xxx does not exist at the time of writing and has not existed in the past. I'm not sure what you mean by "easier" and it's not clear that you fully understand that process of TLD approval or the implications of introducing .xxx. It need not, for example, increase the amount of pornographic content on the internet if that's what you're concerned about (that'll happen anyway!). The more pressing 'risks' are likely to be along the lines of ghettoising a part of the net, where we might end up with ISPs carrying everything but "xxx" sites or governments blocking the domain ("who legitimately wants access to that stuff?", they'll say), resulting in further breakdown of network neutrality and the landscape of the internet appearing differently depending on who provides your connection. This is what occurs to me when I consider the idea of this domain but, as I said, everything in Wikipedia needs to be documented elsewhere to meet the standard for inclusion. 82.32.186.24 (talk) 21:37, 21 March 2011 (UTC)
 * Sorry, 182... If by "ban" you're referring to governments blocking connections to the domain (rather than preventing it coming into being) then I misunderstood you and we're coming at this from the same perspective I think! The bit about including information on risks with reference to reliable sources still stands of course. 82.32.186.24 (talk) 21:41, 21 March 2011 (UTC)

considered essential
Having just read 2004's RFC 3675: .sex Considered Dangerous, I'm firmly of the opinion that the notable concerns raised there about the merits and feasibility of .sex, which has since morphed into .xxx, need to be outlined in this article. I say "notable" because RFCs are issued by people who know what they're talking about when it comes to the plumbing of the internet, and are not coming at this debate from a simplistic and irrelevant "is porn bad?" perspective as seen in some press coverage. I don't have the technical understanding to incorporate the RFC into the article in summary form without the possibility of misrepresenting it, but I'm sure there are many Wikipedia editors who could do the needful. Also, we need a redirect from .sex to this article, since the issues someone looking it up needs to hear about are the same: it is essentially the same proposal under a different name. 82.32.186.24 (talk) 12:35, 29 March 2011 (UTC)


 * It's sometimes s/who know/who are supposed to know/, but this informational RFC was written by an expert in the field. It says that using a TLD to tag content won't work as expected -- if you'd expect say all "museum" topics in .museum, and vice versa, or all German content in .at/.ch/.de, and vice versa.  The ICANN folks were certainly aware of this RFC, and have no unrealistic expectations for .xxx.  The folks trying to get this TLD might have "too optimistic" expectations for their business, but followed the ICANN rules incl. considerable fees.  You could say the rules were wrong to start with, but you'd have a hard time to justify this opinion solely based on this RFC. –89.204.153.230 (talk) 20:25, 9 July 2011 (UTC)


 * (Same unregistered user as above) BTW, if you expect that web pages on servers with a domain in the .mobi TLD are supposed to work on smartphones, and if that works for you (I can't judge it), then this would constitute a counter-example for . –89.204.137.163 (talk) 07:08, 16 July 2011 (UTC)

Missing info the social conservative side of the debate over the .xxx domain
Shouldn't the article include the arguments over the creation of the domain including opposition from social conservatives and anti-porn feminist as well as from governments such as the Obama administration. Also missing is the the response from certain governments over it's creation such as Indian promising to block the .xxx domain country-wide. --Cab88 (talk) 07:01, 6 April 2011 (UTC)


 * I do believe the 'Background' section - essentially a synthesis of arguments pro and con - could be improved. There were arguments against not only from social conservatives, but also progressives fearing censorship implications. But it should be kept brief, and well reffed. If you want to start a 'Reactions' section with the Indian government response, I think that would be quite acceptable. Wwwhatsup (talk) 14:27, 6 April 2011 (UTC)

Categorisation
I see this page is categorised only in the porn categories, not in any technology or Internet categories. I'm not very familiar with how categorisation works on Wikipedia, but surely an article about a gTLD should have some computing categories applied? TRiG (talk) 18:09, 27 June 2011 (UTC)


 * It's categorized as a Sponsored Top Level Domain, that should be sufficient. I've removed "proposed" as it's beyond that stage. Wwwhatsup (talk) 06:36, 28 June 2011 (UTC)

Squatting?
Is it worth having a section on "preventive domain squatting", whereby addresses like "vatican.xxx" are purchased specifically to present them being misused? DS (talk) 13:51, 19 May 2012 (UTC)
 * If we have a good source treating this as a wider issue (rather than the single vatican thing I know of); why not! L.tak (talk) 14:02, 19 May 2012 (UTC)

".sex" listed at Redirects for discussion
The redirect [//en.wikipedia.org/w/index.php?title=.sex&redirect=no .sex] has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at  until a consensus is reached. –CopperyMarrow15 (talk &#124; edits) Feel free to ping me! 23:19, 3 October 2023 (UTC)