Quote:
Originally posted by polish_aristocrat
Ok, my last post about it.
I have no idea what ICANN wants ( probably only the money ) or how serious are the guys behind the .xxx idea.
I am against this idea and from what i know so is still the majority of adult site owners. Not sure why FSC changed its mind, maybe Mr Fiction will enlighten me.
But IMO the main reason that .xxx won't be introdced, is that there is already the .xxx .New .Net domain.
Sure, now only about 20% of browsers support it and ICANN does not have to care about .New .Net at all, but what would happen if .xxx became a tld, when already "many" browsers have .NEW .NET plugins , that cause that when user types in www.sex.xxx he is forwarded to www.sex.xxx.new.net.
I honestly cannot imagine what would happen if ICANN introduced .xxx as an tld - having in mind both legal as well as technical issues.
But certainly my knowledge is limited on these subjects.
|
Good point... ALOT of people have the .new.net extensions installed, even if they don't know it.