Re: [cobalt-users] Call To Arms Against New.Net

["Carrie Bartkowiak" <ravencarrie@xxxxxxxx>]

I've been thinking about this, and it's very disturbing.

Pros: (there's only one)
1. This gives people a way to register cool names like happy.kids.
Which, I agree, we need!  I am all for restricting porn sites to a
.xxx extension; and for putting cool TLDs into place for really
creative domain names.

Cons:
1. When ICANN goes through its next TLD application process and
approves these domain names (which I heartily believe it will; I think
it kept the list small this time to fine-tune the process of adding
new TLDs to the marketplace); which version of the website will we be
sent to? The *real* version registered with an ICANN-accredited
registrar, or the New.Net version?
2. This encourages other server hosts to do the same thing; anyone
with a server can do this. What if everyone on this list suddenly put
their own version of Buy.Com on their server, and offerered a (cough)
"plugin" (registry hack) so that people could see it rather than the
real one? There'd be 300+ versions of Buy.Com floating around out
there. Who's to say that you bought something from the *real* one -
what if your ISP sends you to one of the fake ones and you buy $400
worth of equipment, and that web site owner just takes the money and
never sends you anything?  You're gonna call up Buy.Com raising hell,
and they're not going to have any record of your order, you have no
recourse... etc. etc. etc.
3. Now imagine if you were Buy.Com and the above was going on!!
4. The whole plug-in deal. Keep your hands off of my registry, my
TCP/IP protocols, etc. I'll do it myself if I want to, thank you.  And
the New.Net customers who don't read the fine print are getting
royally screwed - imagine pushing tons of money into a domain name
that most of the world can't see!

As an internet surfer, I am really torn on this issue, because of the
one and only 'pro' to the situation. But as a business owner, I am
flaming mad about it; because this can and will cause all types of
havok, trademark infringement, copyright infringement, slander and
libel lawsuits etc. once ICANN puts these TLDs (and it will) into use.
As an @Home user, I am royally pissed that my ISP would agree to send
me to these domains; knowing what kind of bull can (and will) happen
down the road a year or two from now. I can't believe they'd enter
into something that is bordering on illegal activity... it's not YET,
but once ICANN says okay to .shop (for example) - who's going to be
breaking copyright laws? The New.Net version of somecompany.shop, or
the ICANN version of somecompany.shop??
And as a web host, I have no idea where I stand. Do I support the
people, who are demanding cool new TLDs? Or do I support ICANN, the
non-profit organization that has the only power available to keep
situations like #2 and #3 above from happening?
It's almost like "what the people want" vs. "Big Brother".  To host
them or not to host them, that is the question.

I don't like it at all.
How are the rest of you leaning?  Are you going to host these new
domains, or boycott them?

And yes Dan, I know this isn't Cobalt-related. However, I respect the
opinion of many other web hosts on this list (including you) and I
*really* want to know what the people I respect think about this
issue.

PS - Like I said, I'm on @Home, and I can't see the new domains. So
either they haven't fulfilled their end of the "partnership" yet, or
they just haven't changed the name servers in my area.

CarrieB