| | At Large Membership and Civil Society Participation in ICANN |
|
| |
|
|
|
 YANNA, Yet another new.net announcement
posted by jon on Wednesday August 08 2001, @04:40AM
fnord writes "New.net introduces more meaningful web addresses for Spanish, French and Portuguese-speaking internet users.
More meaningful perhaps, but the same character set. They're still working on non-Roman. It is not my intention to act as a proselytizer for new.net; I have no personal or financial interest in their success or failure, and own no new.net names. If they add new extensions and another 10 million potential viewers every few weeks that ceases to be news. Still, it would be interesting to give the uninitiated an assignment in Namespace 101: Compare and contrast new.net and ICANN."
|
|
 |
|
M. Stuart Lynn is quoted as stating...The reality is, introducing new top-level domains is serious business. It's not something you do lightly.
new.net appears to manage an alternative reality on a regular basis, including a .kids, including a Sunrise, including non-AmerICANN centrification, including enough domains that I've lost count, without a great deal of fuss, and indeed all this since ICANN began own yet unfinished rollout. Even initiates could be forgiven for asking why, then, ICANN goes through millions of dollars, months of pomp and circumstance, months of the ICANN staff micromanaging the roll-out of a few new TLDs, only to have them stumble at every turn. The mountain hath groaned and brought forth a few stunned mice. -g
|
|
|
|
|
|
| |
[ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]
|
|
| | |
|
|
This discussion has been archived.
No new comments can be posted.
|
|
YANNA, Yet another new.net announcement
|
Log in/Create an Account
| Top
| 72 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
|
|
In fairness, it seems to me there are two factors that make it much easier for new.net to create TLDs than it is for ICANN. The first is that new.net is not responsible to anyone, and seems to feel no need to play well with others. The second is that new.net domain names are not valuable; it's the perceived high value of names in the (artificially constrained) ICANN root, together with a fundamentally misguided sunrise policy, that's led to the fiasco we're seeing in .INFO. Still . . .
|
|
|
|
[ Reply to This | Parent
]
|
| |
|
|
Actually ICANN needs to wake up as to what is really going on.
Yes today new.net launched many new extensions. Translations of thier current extensions. Then there is another company www.NameSlinger.com that allows you to register in virtually any domain extension creating new TLDs on the fly. And they check to see if the TLD is "taken" ie in use by another registry in the inclusive and legacy namespaces to minimize conflicts. So it is very possible to both co-opperate with other organizations and provide a virtually unlimited selection in TLDs.
When there is plenty to choose from you do not have the issues that have faced .biz, and .info.
I can see the opposition to the few stunned mice coming from at least two different sources growing and growing fast.
|
|
|
|
[ Reply to This | Parent
]
|
| |
|
|
[ Reply to This | Parent
]
|
| |
|
|
|
Then you can use chandelier.shop.new.net. Not so difficult. BTW, I've had zero problems with the plugin, with Realplayer or anything else, since installing it the day new.net went live. Of course YMMV, and I've seen other reports of problems, but I've also been impressed with new.net's willingness to listen to complaints and respond in a timely fashion, just to do a bit more comparing and contrasting. -g
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
While I am not necessarily a proponent of new.net, I have to say that you are incorrect. New.net domains are, in fact, SLDs and not 3lds. They have set it up so that those who do not wish to use the plug-in or do not subscribe to those ISPs who resolve their TLDs can still see those sites by appending .new.net. It does not in any fashion change the fact that those who "point" to their TLD servers via a participating ISP do not need to append .new.net. They have simply added a convenient method for resolution.
|
|
|
|
[ Reply to This | Parent
]
|
| - 1 reply beneath your current threshold.
| | 6 replies beneath your current threshold. |
Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|
