![]() |
rest in peace! :D
|
Good news. It was a stupid (and corrupt) idea.
Now, get your ICRA tags or similar up on your sites, teach the parents, and lets continue how its supposed to be. :thumbsup |
Did you guys get your money back ?
http://www.xxxregistry.net/ |
Quote:
He had those sharp replies. |
cheers for that good news. :thumbsup
|
Oh shit, I spent $15,000 pre-registering domains! I'm fucked!
just kidding Anyone who did is a sucker, I hope they get their money back. |
Quote:
haha Quote:
Quote:
|
Quote:
from ICM Registry's website: http://www.icmregistry.com/pre-registration.html Notice about potentially misleading pre-registration opportunities ICM Registry has been informed that several so called "registration services" providers may be offering pre-registration for domain names in the .XXX top-level domain. In response, ICM Registry advises that the .XXX top-level domain has not yet been launched, and no registrar or other entity has been licensed or authorized by ICM Registry or ICANN to register .XXX domain names. No party claiming to offer registration services or name reservation services in .XXX can is authorized to do so and any claim by any entity suggesting it has or will have preferential or advantageous access to registration services when .XXX is launched is false. We advise consumers to be very cautious of such schemes and regularly check our website or join our mailing list for updates on availability of .xxx , which will be through ICANN accredited registrars. These types of scheme were also in operation during the last round of TLDs launched by ICANN a few years ago and the problem became so prevalent , the Federal Trade Commission issued the following advisory: http://www.ftc.gov/bcp/conline/pubs/...domainalrt.htm Fight the ...and if you act now, we'lll throw in an extra .XXX domain for the same high price! |
evening bump
:BangBang: Fight the bump! |
Ding dong, the Witch is dead....
|
Cincuenta!.,.......,, :arcadefre
|
great news... .XXX idea was big bullshit
|
Quote:
:) Fight the slipping! |
awesome, that was a fuct idea anyway
|
.KIDS is just as bad an idea as .XXX
Quote:
On a related note ... who decides what is suitable for children - nudity for example is ok in many countries; cultural differences is among the main reasons .kids.US was created instead of .KIDS In my view, any TLD, such as .XXX and .KIDS, that's intended to explicitely restrict content is a BAD idea and asking for trouble. Ron |
I have to agree with the .KIDS idea.
|
.pays would be a cool extension
|
interesting news. thanks.
|
rest in peace...
|
Quote:
yes, .KIDS will have similar issues as .XXX, and while they are birds of a feather in the idea of some kind of restricting of content, how this "restricition" is done is very different. Yes, there will have to be something like an IFFOR that ICM proposed that would have to basically play registry god and decide which websites are able to get a .KIDS domain. I think that guideliness can be crafted that define what is "kid friendly". While nudity in some other countries is more acceptable (and age of consent is lower, etc) , it doesn't pose an issue to .KIDS.. the guildelines would probably forbid such content. I am defining "kids" to the ages of 13 and under (pre-pubescent), who are most likely, could be "harmed" by graphic content. Telling parents to not let their kids on the internet is not a solution. Current blocking software that parents install are not effective solutions. Having .KIDS as a whitelisting blocking approach, would absolutely give kids a safer experience on the web. So if some website that deals with sex education, and feels that kids should know about sex related issues doesn't get a .KIDS domain.. big deal... no one is going to cry for him.. not the ACLU, EFF , or FSC. A hate-speech website would not be able to get .KIDS, etc. There is a massive movement of legislation at both the state and federal levels that seeks to restrict or remove porn from the web. If a happy-medium technological solution is not produced, then legislation and prosecutions will be the tools that are used. So .KIDS does provide for a technological solution to truly keep kids away from the "bad stuff", and i believe, would appease all those looking to do away with porn. Look at Utah and Michigan with their new laws to require ANYONE who sends out emails to scrub against their list, to ensure they are not contacting children. This kind of blacklisting scrubbing is expensive and a logistical nightmare. Imagine that if the filtering was just that if the domain extension on the email was .KIDS that you don't send to it. so [email protected] would easily be removed from anyone's list. For spam .KIDS wouldn't be as big of a solution as for web, because there will be people who will spam a .KIDS address, and there will be those that would specifically target a .KIDS address... But if congress can make can-spam, they could also amend it for the .KIDS extension, and if anyone violates it, then law enforcement has the means to deal with those companies. The "lawlessness" of the internet are becoming smaller, and being pushed into more remote countries, as there is globalization of business and society, and issues like access to porn is of great concern to all countries. Fight the soapbox! |
Quote:
Can't stand someone who has nothing to do with this industry trying to act like he knows what is best for it, all along feeding everyone bullshit and covering up his true intentions, and along the way trying to fuck us all so he can make big. can i sum it up any better ? |
Quote:
actually, Lawley has been pretty much upfront on why he wants .XXX to be approved, to make money on the .XXX domains. what he hasn't been upfront about, is who is behind ICM registry, and where are the "over a thousand" emails from adult webmasters that gave their support as he mentioned in an AVNonline interview. as a registrar on face value of a TLD, they can do anything they want, much like there are many different TLD. They had to sell it as "protecting children" in order to tug on emotional strings... if they just did the approach that it's just another TLD, there were no best business practices attached, then there would have been less friction from the online adult community. They still would have had to deal with the conservative right who feel that .XXX legitimizes porn, and for that main reason, is why .XXX got put to the side. It's more of who supported .XXX is the hidden agenda...because those that publically supported it were few and had their own agendas of using .XXX to regulate porn. Fight the wizard of oz! |
Any time somebody tells me they are doing something "to protect the children," I feel like I'm getting ready to take it in the ass until proven otherwise.
|
One last bump and this thread can go on the back burner like the .XXX TLD
Fight the na na na naaa naaaa hey hey heyyyyy goodbye! |
w00t w00t!!!!!!!!! :thumbsup
|
Good news.
:thumbsup |
|
another bump.
Fight the too many threads! |
this is a nice way to start the holidays :)
|
Quote:
OMG OMG OMG.... WAAAAAAAAAAAAHAHAHAHAHAHAHH!!!! :1orglaugh :thumbsup |
Rumours are that the ICM folks are still lobbying hard on ICANN.. seems to be quite a battle going on..
You have basically all the ICANN members outside of the US complaining that ICANN is a US-controlled entity, and want the UN to run things.. and are opposed to .XXX to use it as their political tool to gain some kind of leverage. You have right wing religious folks hell-bent in their email campaigns to ICANN to reject .XXX as well since they feel it legitimizes porn. All of this overwhelming votes against .XXX by diverse groups, including those companies that took a public stand and listed at http://www.FightTheDotXXX.com was helped only by a last minute call by the Chairman. It seems that ICM had a majority vote of ICANN directors, but then squashed at the last minute by the chairman... who was probably seeing that something funny was going on when so many didn't want .XXX. ICANN is certainly in hot waters over .XXX and critics of ICANN for all these years are jumping in to add to the bonfire. Further what is interesting, is a report from ICANN recent meeting had several blackened out paragraphs on .XXX that apparently ICM/ICANN didn't want people to know about. I am guessing these had names of companies that gave their support or businesses that had connections to ICM got the black marker in the PDF. Fight the things that make you go hmmmmmmmmm! |
All times are GMT -7. The time now is 01:49 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123