Slashdot Mirror


.NAME at a Crossroads

An anonymous reader writes "It seems the .NAME registry is at a crossroads. They say that things are going far from well, and so they have started their own registrar that is going to try to market .NAME domains to individuals, unlike all other registrars. If they don't manage, this will be the first gTLD to go bankrupt. I guess that will put a damper on any plans to introduce more new TLDs."

59 of 289 comments (clear)

  1. Well,... by ksheka · · Score: 2, Funny

    ...what's in a name?

    (OK, someone had to say it. :-)

    --
    alias uptime="echo '5:33pm up 22342352324 days, 6:28, 2124315623 users, load average: 2432.40, 12312.31, 123123.19'"
    1. Re:Well,... by Xandar01 · · Score: 2, Funny

      > ...what's in a name?

      A .com load of debt?

      --
      Life moves pretty fast; if you don't stop and look around once in a while, you could miss it. -FB
  2. Selling to individuals is good by xadhoom · · Score: 3, Interesting

    I've never taken my .name domain just because they don't sell directly to individuals. But now, I have a chanche. I think that's a good idea, but the news should be promoted *alot* .

    --
    I was there.
    1. Re:Selling to individuals is good by capt.Hij · · Score: 2, Insightful

      There is not much incentive for individuals to get this. Broadband seems to be the fastest growing way to establish a full time internet connection. Most broadband suppliers do not want people running servers on their networks. What would be the point of buying your own name when you can't flaunt your vanity by actually using it!

    2. Re:Selling to individuals is good by raju1kabir · · Score: 2, Interesting
      But once one person have bought smith.whatever, the remaining 3 million people with Smith as their lastname will be out of luck. Hence .name, where all of them still have a chance at getting their firstname@smith.name

      In other words, it's a totally useless service and I can't imagine anyone using it. You can get a proper domain from anyone else and do what you want with it, and do it properly. Why pay for this crippled version where you have to depend on servers run by some unknown entity with unproven email/web server expertise to pass your mail/web traffic along? I wouldn't use this for my personal snapshots-of-friends-weddings site, let alone something connected to my work as an author or artist.

      The reason this is doomed to failure is because the only people whose needs are so shallow that they'd accept this arrangement, don't care enough to go to the trouble and spend the money, especially for something they can't really understand.

      This enterprise will be belly-up by the year's end. They can go hang out at the bar with the Realnames people.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    3. Re:Selling to individuals is good by vidarh · · Score: 2, Informative
      Exactly, and that's the focus of Personal Names: To let you set up a .name without anything except for an existing e-mail address and (if you choose) and existing web page somewhere (whether on it's own server or on a free webhosting service). When you register, you get to enter your forwarding addresses, and you can log in and change that at any point afterwards.

      It's meant to be incredibly simple, and it seems to work - we're seeing a good amount of registrations (and btw. <shameless-plug>we have an affiliate program</shameless-plug>)

      (Disclaimer: I work for Personal Names)

  3. Advertising! by Anonymous Coward · · Score: 4, Insightful


    Dang, I've never even *heard* of .NAME before. Just asked 2 coworkers, they haven't either.

    Well shucks, I just can't figure out what the problem is...

  4. Does anyone have one? by krony · · Score: 5, Interesting

    Seriously, does anybody here actually have a .name TLD for their website? More specifically, do you have a .name without the corresponding .net, .com, or .org?

    1. Re:Does anyone have one? by vidarh · · Score: 2, Informative
      Try searching google for "site:name -dfgdfgadfgaagdfg", and you'll find lots of .name site. Nowhere near the other major TLD's, but growing at a reasonable rate.

      (Disclaimer: I work for Personal Names)

  5. I want this URL by addaboy · · Score: 5, Funny

    http://whats.my.name/bitch or http://say.my.name/bitch

  6. I'm too late by johnburton · · Score: 5, Insightful

    My name has already gone so I couldn't have it even if I wanted it. There is no point having a variation of it either. I can't imagine how they expect this to succeed. There are far too many people with the same names, You need a proper hierarchy for this kind of thing.

    --
    Sig is taking a break!
    1. Re:I'm too late by FearUncertaintyDoubt · · Score: 5, Funny
      My name has already gone so I couldn't have it even if I wanted it.

      I know how you feel. I got muscled out by that guy John Jacob Jingle Heimer Schmidt. His .name is my .name too.

  7. to market the .name tld? by _anomaly_ · · Score: 2, Funny

    maybe it's just me, but i saw a bunch of marketing from my registrar (register.com) for the .name tld.

    so much, in fact, that i went ahead and registered mine... and haven't done a thing with it since (it's been probably almost 2 years now maybe). this is mainly due to the fact that i'm lazy and not sure what to do with it... but still seems to be the norm for the .name tld.

    --
    "I have no special gift, I am only passionately curious." - Albert Einstein
  8. We then need a new gTLD by spacefight · · Score: 5, Funny

    .bankrupt

    nuff said

  9. Who wants anything but .com? by Mike+Rucker · · Score: 3, Insightful

    I guess .net and .org are ok too but only if you also have the corresponding .com. If you get anything other than a .com then everytime people try to go to your website they are going to type it in wrong until they remember your strange extension.

    1. Re:Who wants anything but .com? by LordWoody · · Score: 4, Informative

      Me. Some of us still follow the distinction that the original tlds had (.edu for schools, .com for commercial, .net for networks, ISPs, etc..., .org for organizations such as community orgs, non-profits, etc..., and so forth).

      While I think the whole tld was a terrible idea applied in an even worse fashion, I still register my domains based on what general tld they best fit. I have no interest in leading people to believe that our LUG is a commercial interest or that my business is some community group or non-profit. Although I am not above availing myself of the .us tld if that is the only non-misleading tld left for a given name.

      With the advent of search engines like Google, the whole "what cool FQDN is your site?" is becoming irrelevant anyway.

      --
      Never meddle in the affairs of dragons,
      for you are crunchy and good with catsup.
  10. They aren't doing it right. by z_gringo · · Score: 4, Interesting

    Either that or I don't understand. (It works out the same for me in the end).

    I went to register my .name, just for kicks, I entered Z for my First name, and Gringo for my last name, and I was provided with the very helpful message:

    Your own, impressive .name addresses
    z@gringo.name; and
    www.z.gringo.name
    may be available right now.


    Which isn't really what I would want at all, IF I did want a .name. I would want zGringo.name

    Their version of "whois" isn't really what I'm used to.. Maybe that's the way it's supposed to work, but then, that also probably what I'm not really interested in a .name.

    And, what's up with their response: www.z.gringo.name
    may be available right now
    ?? Is it available or not? It was a yes or no question..

    argh..

    --
    -- -- Warning. Do not stare directly at the sun.
    1. Re:They aren't doing it right. by anticypher · · Score: 2, Interesting

      the .name service should all be put to death (in a texas department of corrections sense of the word) for their crimes against the internet community.

      Really, what they have done is squat on tens of thousands of names, in the hopes of extorting a few services from the masses. They don't offer traditional DNS services, where someone types in a name and the resolver returns the IP address of your name server, they are offering only email and web redirecting services. Nothing else.

      I want anticypher.name to point to my name server, but they won't do that. They will give me a heavily spammed anti@cypher.name email forwarding service, or a web redirector with WWW tacked on the front. I know a few people who stupidly signed up for these services, and got a torrent of spam afterwards because they are then marked as gullible, naive idiots, the scammers choice of easy victims.

      The whole service should die, the sooner the better.

      the AC

      --
      Hemos is like...sci-fi fans;he thinks technology is cool, but he hasn't bothered to understand the science it's based on
    2. Re:They aren't doing it right. by FTL · · Score: 3, Informative
      > They don't offer traditional DNS services, where someone types in a name and the resolver returns the IP address of your name server, they are offering only email and web redirecting services. Nothing else.

      I'm sorry, but Slashdot really needs a '-1 Wrong' mod point.

      The .name TLD will sell you any third-level domain that you want. Just like *.co.uk or *.ny.us does. The DNS lookups are perfectly normal. The email is perfectly normal. What more can I say ... what you stated is completely untrue.

      And yes, I do know what I'm talking about. I'm a sysadmin, and owner of my own .name website. Go ping it.

      --
      Slashdot monitor for your Mozilla sidebar or Active Desktop.
  11. Free the namespace! by Ashurbanipal · · Score: 5, Insightful
    If they don't manage, this will be the first gTLD to go bankrupt. I guess that will put a damper on any plans to introduce more new TLDs.
    Hopefully it will only put a damper on plans to introduce stupid TLDs that perpetuate the expensive stranglehold on naming that ICANN enjoys.

    TLDs should be available to anyone who can run a secure, reliable root - this connects profit to performance, so we don't have to rely on the innate goodness of the root nameserver operators. The first thing that'd happen would be that pepsi.com, pepsi.net, and pepsi.org would be obsolete since .pepsi would be run by PepsiCo.

    With the widespread popularity of search engines, nobody would have any trouble finding anything even if some temporary chaos were engendered.

    Spare me the FUD about nameservices not scaling for this; I believe DNS and BIND are quite capable of it.
    1. Re:Free the namespace! by Fastolfe · · Score: 3, Insightful

      The DNS software isn't the problem here. What you're recommending is basically a flat DNS namespace, where 90% or more of the present-day DNS traffic is moved directly to the root servers. You're going to need to beef up those root servers several orders of magnitude in order for this scheme to work. This has another order of magnitude impact on the survivability of DNS in the event of network problems. You've just increased your reliance on the root servers significantly, since it's unlikely your local caching DNS server will have names cached for every DNS request you make.

      DNS is hierarchial for a reason, and the number of TLD's was small for a reason. The root servers should just need to be probed for a limited set of names, and from that set, it delegates to another set of servers, which delegates to yet another set.

      Changing this primarily hierarchial arrangement to a primarily flat one (with some hierarchial vestiges left over, since you'll probably want www.pepsi to work "just in case") would require a fundamental restructuring of DNS and would impact reliability and performance in a very noticable fashion.

      A more extensible, future-friendly option might be to put DNS back the way it was 10 years ago and build another distributed database designed to map real-world names to Internet domains.

      I should be able to use this database to look up the name "Pepsi" in a business context, and have it return "pepsico.com" or something. A DNS SRV lookup on pepsico.com for the 'http' service might return "www12.web-farm.public-facing.pepsico.com" or some other company-specific hostname representing their web servers (it doesn't have to be a vanity "www.pepsi.com" since users don't need to see this anymore). My browser would then connect and I'd get "Pepsi"'s home page, not the home page of "pepsi.com". We need to start breaking this huge reliance on DNS names as a locator service and put DNS back to work at what it was designed to do: to put an alphanumeric label on Internet hosts.

  12. Re:Die .name, die! by morgajel · · Score: 2, Interesting

    I agree.
    Within 70 miles of my house, I accounted for 4 people besides myself that had the same name as me. Two even had the same middle initial.(This was the first thing I did when I was exposed to the internet for the first time way back when).

    Now, my name isn't exactly common(Jesse), which makes it even more annoying. Spam for .name is a very LAME idea because names aren't unique, and most people know this.

    --
    Looking for Book Reviews? Check out Literary Escapism.
  13. Anonymous.Coward.name by Fulkkari · · Score: 5, Funny

    No one seem to have registered Anonymous Coward, even though Slashdots seems to be full of people with this name. How is this possible? You would think that at least one of these several hundred Cowards would register with their name. Things must be going really bad for .name...

    --
    I demand the Cone of Silence!
    1. Re:Anonymous.Coward.name by random_rabbit · · Score: 5, Funny
      That reminds me. Last night my girlfriend said "I think that this Anonymous Coward guy spends far too much time on this site. He's all over it".

      I wanted to agree, but I was too busy getting beaten for laughing at her.

  14. Is that surprising? by t_hunger · · Score: 4, Interesting

    Well, it does not surprise me... having a own domain is cool, I know. But john.doe.name just sounds stupid. And the more common names should be taken allready anyway. How they they handle that? john.smith294.name? Definitly uncool:-(

    The registrar claims it is for indivuduals to register their name. I just tried "www.john.smith.name" und ended at www.smith.com, some company website. Doesen't that spoil the purpose?

    Finally the website of that registrar claims that john smith "may be available right now." It's not, or it wouldn't redirect me to that company website. Why doesen't the registrar say so? What good is that query field if it cannot even figure out names that even my DNS server knows to be taken?

    Now instead of this ridiculous ".name" they should have introduced ".sex" and forced all those sex-companies into that TLD. That could have helped parents to make sure their children do not get exposed to lots of the smut on the net and I'd be happy with just blocking all mails from "*.sex" and have way less spam in my inbox. Of course that wouldn't have worked out completly -- someone is bound to try to offer adult content under other TLDs -- but I'm sure it would have helped.

    --
    Regards, Tobias
    1. Re:Is that surprising? by raju1kabir · · Score: 3, Insightful
      Now instead of this ridiculous ".name" they should have introduced ".sex" and forced all those sex-companies into that TLD. That could have helped parents to make sure their children do not get exposed to lots of the smut on the net and I'd be happy with just blocking all mails from "*.sex" and have way less spam in my inbox. Of course that wouldn't have worked out completly -- someone is bound to try to offer adult content under other TLDs -- but I'm sure it would have helped.

      No, it's very stupid and it wouldn't help at all. I don't say this to be insulting, but because this supposed panacea is constantly being brought up by people who can't or won't think things through.

      People selling smut want to get it under the noses of as wide a potential audience as possible. Hence the existence of things like www.whitehouse.com. You will not be able to stop them or even put a dent in their operations unless you manage to outlaw porn in general worldwide, which is (A) bad policy, and (B) highly unlikely. If you create a .sex domain, then the porn operators will register in both - it costs them $10 and gets them more exposure.

      If you want to provide a child-friendly environment, you can create a domain called .kids or whatever. Require organizations registering in it to either provide references from established child-friendly outfits (school system, CTW, etc.) or to post a large cash "smut bond". Anyone found with porn on a site reachable via a .kids URL (whether it's because they ran an open web proxy, or because they willingly put it up) forfeits their bond and loses their domain.

      This works, because you have a finite number of domains to monitor, and you have specific disincentives to leverage. Trying to keep pornographic content out of the "rest of the internet" is an impossible task and only an idiot (or someone with a fat non-outcome-based contract) would attempt it.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    2. Re:Is that surprising? by toastyman · · Score: 2, Insightful

      No offense, but I don't think you really understand the "adult" industry on the web.

      Not all of us want to spam you with our website.
      Not all of us want to trick you into visiting, or deluge you with popups should you ever commit the horror of trying to leave the site.
      Not all of us have a blatant disregard for wanting to keep kids out of our sites.

      Personally, I'd love to transfer EVERY domain we have over to a ".xxx" or ".adult" or ".sex" or whatever TLD. Existing *.com domains we'd setup to redirect to the *.xxx version.

      Yes, something like this would be voulentary, and yes there would be people out there who wouldn't do it. However, I'd love there to be a way that we could easily segregate our adult sites away from the rest of the internet, so that those who DO want to block such things can do with a reasonable accuracy.

      It really could go either way. With a *.xxx policy, you'd have very few false positives (who would register and use their .xxx domain, knowing that many people would block it?), but a decent number of false negatives until it caught on.

      With a *.kids policy, you knot only have to have someone very STRICTLY controlling its use (or it becomes useless), you'd be forced to limit browsers use to just *.kids if you wanted to play it safe. That's not going to leave much of the internet left until it had a real critical mass going.

      You'd also have to deal with the sticky subject of what exactly IS .kids material? What's okay for 15 year olds isn't okay for 7 year olds. Whose idea of what's acceptable do you use?

      99.99% of the adult webmasters out there would LOVE a way to keep kids out of the sites. We would love a simple check box that every ultra-conservative letter-writing crusader could check that would make sure they never saw our sites. Yes, we use ICRA style tags that are meant as content advisories to browsers, but every attempt at making THOSE known to users have failed.

      I can understand some of the reasons people have for not wanting an "adult only" tld, but I think its use would have a much greater public good than... oh, say... .aero?

  15. Now I have to pay attention to TLDS - agggh by jj_johny · · Score: 4, Interesting
    The fundemental problem that .NAME faces along with the rest of the internet is no garbage collection. These new TLD are pretty useless when you have to make sure that people remember the ext. When it once was default that if you worked for a company, your email was some variation of your name, the at sign and some variation of the company name and then you assumed the .com. If you worked for the gov or an organization, it was pretty clear what its end was. (At least in the US.) But now you have all these bloody domain names that everyones significant email and web address is now 4 or 5 characters longer.

    Next they will try a TLD with umlauts and maybe some of the cyrilic letters.

    1. Re:Now I have to pay attention to TLDS - agggh by Tim+C · · Score: 2, Insightful

      Next they will try a TLD with umlauts and maybe some of the cyrilic letters.

      And what exactly would be so wrong about domain names in non-ASCII character sets? If you can't read the language, then there won't be anything there for you, so why do you care? If you can read the language, then isn't it a good thing to be able to have a domain name in your own language, without having to transliterate it into a foreign character set?

      The web was supposed to facilitate communication, not force everyone into a single character encoding for no better reason than the country that developed it used that one.

    2. Re:Now I have to pay attention to TLDS - agggh by Fastolfe · · Score: 2, Insightful

      There are two schools of thought here.

      The first advocates a "lowest common denominator", where hostnames are explicitly restricted to a subset of the world's scripts. Some will have little or no problems with this (e.g. Americas and most of Europe) while others may have to transliterate significantly.

      The second advocates a full internationalization of DNS, allowing hostnames to be represented in any and every script imaginable. Nobody would need to adapt to any lowest common denominator, since they can just use names in their native scripts.

      The first approach encourages interoperability at the expense of those furthest away from the standard (e.g. asian scripts). The second approach encourages expanding language barriers into the area of Internet hostnames.

      With multiple scripts in DNS hostnames, it's now difficult for me to correspond with an abuse contact at a provider in an asian nation, because I can't type their e-mail address. This is a very bad thing.

      I might not have a problem with this approach if the world didn't have this immense reliance on DNS hostnames. If we had another directory sitting atop DNS, mapping real-world names to DNS domains, and a more integrated database of contacts and Internet resources, I shouldn't have to type or cut-and-paste much of anything in the future, and this wouldn't be much of a problem. By the same token, however, users will be abstracted away from DNS hostnames for the large part, reducing this perceived need for hostnames in multiple scripts. We can then go back to technically-oriented reasons for why this is or is not a good approach, and these seem to strongly favor interoperability, which, at the moment, favors a lowest-common-denominator approach.

  16. What I'd Like to See by syr · · Score: 2, Interesting
    The only second generation names I'd like to see would be .kids and .xxx. These two TLDs would solve more problems than they would create, imo. It wouldn't necessarily cause a policing effect on the Internet but it will help narrow potential searches for children and adults to sites that they were actually looking for in the first place.

    I'd hate to see what kind of *.xxx domains get picked, though. And for that matter I'd hate to see some of the scary things placed under .kids.


    Syr GameTab.com - Game Reviews Database

  17. Advertising? Technical issues? by Tokerat · · Score: 5, Insightful


    Until this article I had never even heard of a .name TLD. Perhaps if more people knew it existed? Most average people are still stuck on .com anyways. I tell them my website's address, 4am.kicks-ass.net (yay DynDNS), which ends in .net, and they call me up complaining it doesnt' work. Some of them put .com, some of them actually put .net.com, and still others put www.4am.kicks-ass.com. Point being, how many people are going to get bounced e-mails from frank@rizzo.com or frank@rizzo.name.com?

    Also, once I get this TLD I need to do something with it. After I pay for hosting or a mail server setup (which is what most people woudl probably want a .name for), this becomes a little more expensive than simply being "gt3trkj3p6@verizon.net"...

    --
    CAn'T CompreHend SARcaSm?
    1. Re:Advertising? Technical issues? by Darnit · · Score: 2, Insightful

      I checked out the website and it is confusing me. If I type in my name in the box "Tim" "Darnit" it says that I can get Tim@darnit.name and tim.darnit.name. What does that get me? Do they delegate tim.darnit.name to me or darnit.name. Do I have to have the email forwarding? If I set up my own domain with tim.darnit.name then I would only be able to give out buelah@tim.darnit.name to my wife. To be Buelah@darnit.name she woiuld have to pay for her own stuff. Am I correct on this?

      This must be marketed to more mainstream net users and not people like me.

  18. No surprise? by Jugalator · · Score: 5, Interesting

    I think this post summarizes the outstanding problems well.

    Two points from that post:

    - .NAME is a TLD targetted for individuals, but priced for organizations, even if .NAME DNS requests should be far less common than .COM lookups.

    - .NAME in your e-mail let spammers easily detect individuals, merely by looking in a phone book and putting an @ between the forename and surname, and finally applying .NAME.

    --
    Beware: In C++, your friends can see your privates!
    1. Re:No surprise? by vidarh · · Score: 2, Interesting
      Considering how spammers can easily autogenerate spam lists for most of the major ISPs by following easy to guess allocation patterns, I don't see why your name would be any easier.

      (Disclaimer: I work for Personal Names)

  19. They do (sorta) by kikta · · Score: 2, Informative

    The current scheme appears to be that they aren't selling domains, per se. After visting the link (which gives you a list of registrars), I found that no one will sell me "kikta.name". However, all seem to let you buy something in the form of "jason.kikta.name" (which comes with an email address of "jason@kikta.name"). So they're not really selling personal domains, just "firstname.lastname.name". If anyone can find anything different, please say so, but I tried 5 of them before I gave up.

    FYI, "scream.my.name", "whats.my.name", and "say.my.name" are all taken already. ;-)

    1. Re:They do (sorta) by vidarh · · Score: 2, Informative
      No second level names can be bought under .name from anyone. So yes, you do get a domain, but it will be on the third level, just as it is for for instance .co.uk, and in a lot of other cases. It's no less a domain name than something at the second level, and it is regulated by ICANN just as any second level .com.

      (Disclaimer: I work for Personal Names)

    2. Re:They do (sorta) by hucke · · Score: 2, Interesting

      Does a person registering within .name get full control of an actual domain - with the ability to create usernames at will, change the nameservers, etc.?

      Someone buying "john@smith.name" owns only an email address within a domain he doesn't control. "john.smith.name" is a bit better - if this is actually a domain name that they'll have full control over. If it's just an "A" record in your server, it's not a good deal.

      These names have less value than any other domain. I initially registered "hucke.org", years ago, so I could have "matt @ hucke.org"; since then, I've given email addresses within that domain to my mother and brother, at no additional cost. I still pay only $13.50 a year for that domain, regardless of how many addresses or subdomains I create within it. Can john@smith.name do that?

      "John Smith" may have a slightly better chance of getting john@smith.name than he would johnsmith.org - but that remains true only as long as .name remains unpopular. If .name domains ever did become popular, you'd suffer from the same unavailability of names as anywhere else.

      And john@smith.name still can't add an address for his wife or mother without having to pay an additional fee.

      For $19.95 a year, you're delivering a product with *less* value than registrars in other TLDs.

    3. Re:They do (sorta) by vidarh · · Score: 2, Informative
      Yes, you get full control over the third level domain, with the ability to create usernames at will and change the nameserver etc. Currently Personal Names Ltd. handle that functionality via e-mail to customer service, as most of our users prefer to just use the web forwarding we provide.

      You're right that someone buying john@smith.name doesn't get control over smith.name, but yes, you would own john.smith.name, just as you'd own johnsmith.com.

      As for adding additional addresses - you either need to do so under the third level name, or buy another e-mail forwarding. That's how .name is structured in order to give more people a chance at their lastname (try getting a common lastname under .com, for instance)

      As for less value, if you can get your firstname@.com, sure, go ahead. For most people, that is not an option, as their lastname was registered years ago. We're giving people another chance at that a reasonable address. If they don't think it's worth it, then that is obviously their right. So far, however, our research indicate that people aren't particularly bothered about the price - either they want it and the price isn't an object, or they don't.

      (Disclaimer: I work for Personal Names Ltd.)

    4. Re:They do (sorta) by vidarh · · Score: 2, Insightful
      The point is less than 1% of our customers have even asked about the availability of features like that yet. Most of them wouldn't know what a name server is, or what a domain name is. It wouldn't be cost effective for us to postpone launching the service just in order to get in place features that most of our paying customers couldn't care less about, and wouldn't even understand.

      This is something many Slashdot users seem to get wrong: Slashdot users are generally not particularly attractive customers. Sure, there are many people here, but most people here show around for price, complain a lot, are power users that require tons of features normal users aren't interested in, and generally don't like to pay for stuff they can do themselves for free or cheaper.

      In other words, while we're happy to take any customer that want our product, and will happily help more advanced users, it would be economic suicide for us to try to cater for Slashdot users instead of people that are less demanding, less price sensitive, more willing to spend and hundreds of times as many.

      There are certainly services for which Slashdot users would be the right primary audience, but this is not one of them.

      (Disclaimer: I work for Personal Names)

  20. .name TLD has incompatible site! by Vadim+Makarov · · Score: 2, Insightful

    Any TLD authority whose site doesn't work in Netscape 4 looks cheesy to me... (reach for IE) and the one that requires Flash definitely won't be on my list. Period.

    --
    17779 eligible voters in a district, 17779 'vote' as one. This is Russia.
  21. Re:.NAME and owership rights? by vidarh · · Score: 2, Informative
    .name uses a dispute resolution method that give you automatic right of ownership to the name you have registered if it is your own name, the name of a deceased person that you have the right to control (for instance as the executor of an estate) or the legitimate trademark owner of a fictional name.

    So if you really are John Smith, and registered john.smith.name, noone else named John Smith could take it away from you.

    (Disclaimer: I work for Personal Names Ltd)

  22. Gee, why *IS* it failing? by Asprin · · Score: 3, Funny


    It looks like they left off a reason why sales are slow: because it's a stupid idea!

    How many people really want a personalized email domain that maps directly to your real name, cannot be changed and therefore says "HEY, SPAMMERS, I'M OVER HERE AND I DON'T GET ENOUGH CRAP IN MY EMAIL!!!!!"

    I don't know what bothers me more - that they thought it was a good idea to begin with or that they think it just isn't being marketed well enough.

    BTW, I *fully* expect that before they cash out and go home, we'll hear that they tried to market their customer database to spammers, not realizing that a 1 line perl script could generate a list of valid addresses of the form 'john@smith.name'.

    What a bunch of maroons!

    --
    "Lawyers are for sucks."
    - Doug McKenzie
  23. YRO? by sporty · · Score: 2

    Having .name is a right? I thought free speech was a right, at least according to the constitution.

    Bush, did you slip the .name registry in the constitution again? Bad bad president.

    --

    -
    ping -f 255.255.255.255 # if only

  24. the.site.with.no.name by wowbagger · · Score: 5, Funny

    the.site.with.no.name - be a good Spagetti Western homage site.

    theyve.given.me.a.number.and.taken.away.my.name - The Prisoner and Secret Agent Man homage site.

    went.through.the.desert.on.a.horse.with.no.name - fan site for the band America.

    a.policeman.knew.my.name - Site for The Who.

  25. Because it's against the rules by magicianuk · · Score: 2, Informative

    You can't have john.name (the same way I can't buy magician.uk, I can only buy magician.co.uk (which I did))

    It's firstname.lastname.name and basically that's all they allow. In theory it has to be your real name too, but somehow I managed to get the.magician.name as well as my real name, but it does leave me with an email address of
    the @ magician.name which isn't terribly good.

  26. Re:I have my own .name domain by clarkcox3 · · Score: 3, Funny
    It would be a shame if it folded, but since I mainly bought these as "vanity" domains and don't publicise them, I wouldn't be too upset if .name went away ...
    You call posting to /. "not publicizing"? :)
    --
    There are no tiger attacks in my area and it's all because this rock I'm holding keeps the tigers away.
  27. One problem with the .name TLD is... by krouic · · Score: 2, Interesting

    ..that it contains 4 letters instead of 3 or less for the other common TLDs.
    I have had my .name email address refused by several on-line purchasing systems, because some dumb programmers decided that an email address that had more than 3 characters after the last dot was invalid. So I have had to get an alternate address to be able to access these sites.

  28. A BIG warning by Gudlyf · · Score: 4, Informative
    I signed up for a .NAME domain, stupidly through Network Solutions, for a fairly high price. This was because other registries such as Go Daddy weren't registering domains under .NAME at the time (I hear they do now). I was being all hasty about things, and decided to nab my .NAME ASAP with NetSol.

    The price NetSol charges, like with anything else, is outrageous, but that's not the worst of it. When I tried to have the domain transferred to Go Daddy (much, much cheaper), I found that I can't! In fact, what I believe happens is that once you apply for your .NAME domain (i.e., john.smith.name), NetSol takes ownership of "smith.name", and you're given the right to use the "john" subdomain -- it can't be transferred! (or, at least, they're not allowing it)

    NetSol also makes you purchase email hosting with the domain, and tries to tack on some web hosting. Simply put, DO NOT go through NetSol for this service. (I can hear the collective, "Well DUH!" now)

    This is why I'm letting my .NAME domain dry up and die, and will continue to handle my email the way I always have. There's no way in hell I'm paying NetSol's outrageous prices until I'm able to transfer to some other registry.

    --
    Trolls lurk everywhere. Mod them down.
    1. Re:A BIG warning by vidarh · · Score: 3, Informative
      Luckily, you're wrong. The second level (smith.name) is NOT delegated from the registry. You have a right to transfer your name, unless your contract with Netsol says something else.

      I suggest you contact GNR (the registry) and talk to their customer service people to get help in getting it resolved.

      (Disclaimer: I work for Personal Names, the registrar mentioned, and we're a competitor to Network Solutions)

  29. I use .name domain and e-mail... by Przepla · · Score: 4, Interesting

    ...and I will be very unhappy if it disappear.
    First of all, I want my own domain and since I am not an ORGanization, not a COMmercial business, not a NETwork backbone .name suits me very well.

    I use it since beginning and I receive very little spam (while I post to USENET without even spamblocking my e-mail).

    If I would buy .com domain my personal data will be reavealed in Whois database, so I don't care if my name is put in e-mail itself or not.

    And finally now I can switch from different ISP without changing subscription addresses, my Bussiness Cards, and sending e-mail to all my friends about new e-mail.

    I can agree with one thing, it is not properly advertised. But did you hear about .museum, .coop or .aero domain?

    Note: English is not my native language, so please disregard any spelling or grammar mistakes.

    --
    When in doubt, go to the library. - Ron Weasley in Harry Potter and the Chamber of Secrets
    1. Re:I use .name domain and e-mail... by SparklesMalone · · Score: 2, Informative

      I too use .name, and frankly I couldn't care less about people figuring out who I am. I only give my .name address to friends and associates and use a throw-away Hotmail account (or nothing) for more public spaces. If I want to post anonymously I deserve to be labelled "anonymous coward". If I have the guts of my convictions I should have the guts to put my name on it too. The print press has it right; if you want mass readership (letters to the editor) you've got to fess up to who you are.

      Democracy demands it. Gov't of the anonymous, by the anonymous, and for the anonymous? How do you know 50,000 "Invade Iraq" posts to the Washingon Times aren't generated by Haliburton?

  30. Re:Die .name, die! by Zeinfeld · · Score: 4, Insightful
    You mean I won't get any more .name spam??? Good, let it die! .name was a lame idea anyway.

    The problem is the spam. Very few people want to have their cyber identity tied to their email address in such a direct fashion.

    The .name zone has about 10,000 Web pages in it. So you can work out the number of domains they have probably sold.

    The big problem that the new registries face is that they thought that starting a new domain was a license to print money for doing nothing. They simply did not expect that there might be some actual work involved.

    $35 sounds a lot by geek consumer standards, but you need a minimum of 2,000 names to cover the cost of hiring one person at that price - including salary, overhead, benefits etc. You need a minimum of 5 people to provide round the clock support.

    The business models of the new domains expected people to buy millions of them in the first year. They did not understand that maybe it might take five years to build a critical mass.

    It is always easier to look at someone elses business, particularly a successful one and decide that it is essentialy easy to run and cost free than to have your own idea. Look at all the folk who blundered into etail thinking that the economics of that space would somehow be different to the economics of mail order, a business notorious for its low margins and high infrastructure costs. Or look at the folk who blundered into home delivery of groceries, an even lower margin business, building $30 million distribution centers to serve markets that could not possibly support the interest payments, let alone register a profit.

    Folk who have .name domains should not be too worried however. The same thing happened to .tv which spent through its initial VC funding at record pace and was bought out for about a tenth of the amount spent on building the brand. Someone will buy .name, although bidding is not likely to be brisk.

    --
    Looking for an Information Security student project suggestion?
    Try http://dotcrimeManifesto.com/
  31. This has been tried before by madstork2000 · · Score: 3, Informative

    I worked for a startup that was selling "third-level" domains to doctors under the .md domain. The company purchased severalthousand .md domains that represented "surnames". So we owned "smith.md", "wilson.md", etc.

    We provided web hosting (http://www.john.smith.md), email (john@smith.md), easy to use templates, for non tech savvy doctors.

    Several issues worked against us. First the company controlling the second level domains (i.e. the "surnames") that we had to purchase, charged too much for the business model (upwards of $300 /per year for a single second level .md domain).

    The other issue was we couldnever have all the names. so we could not do large "instatutional sales" effectively.

    these first two issues shouldnot effect .name, but the other issues we had problems with would:

    1. Name Overlap -names are not unique, we never achieved a large enough user base for this to be much of an issue, but it did come up occasionally.

    2. SPAM- the addresses are pretty easy to guess, since first@last is pretty easy to guess. the other SPAM issue was that more and more ISPs require the outgoing mail address to be on their network, and sothe users needed to configure the IMAP/POP accounts to use our sevrers, rather than their local ones.

    3. User ignorance, the way the email was/is built of the second level domain (john@smith.md) and the website is off the third level - john.smith.md confused the users, the sales people, and management. We never effectively explained the subtle difference to non savvy users.

    4. Long names. http://www.john.smith.md is an ok sized domain name,but if you had a long orhyphenated name, the email address and domain name become excessively long, and awkward to work with in "real world" applications,likeputting on business cards and letterhead.

    In short it sees the .name folks are making some of the same mistakes, and not addressesing the inherent problems needed to overcome the issues.
    In retrospect there are several more trouble issues that both our .md plan and .name share,
    but no sense in beating a dead horse, they definately need some help, some luck, and cash if they expect to succeed.

    I wish 'emluck cause I think they will need it...
    -MS2k

  32. Other TLDs? (slightly OT) by PontifexPrimus · · Score: 2, Interesting

    Quick question:
    What happened to the other new TLDs (.aero, .biz, .coop, .museum, .pro, .grumpy and .sneezy)? I don't consciously remember ever seeing one of them - just like I never saw a .name URI. Why introduce all this crap at all if no one uses them?
    (Oh, and don't bother checking out www.canna.biz. It's already taken...)

    --
    -- Language is a virus from outer space.
    1. Re:Other TLDs? (slightly OT) by vidarh · · Score: 2, Interesting
      .biz and .info are doing pretty well (closing in on a million registrations), .name is lagging a bit behind, the rest are still very small, but that's to be expected considering their special nature. The closest comparison would perhaps be .int - how often do you visit .int sites? Yet some very large organizations use .int domains as their primary internet presence.

      Remember .com had about a 15 year head start...

  33. Google makes this pointless by djKing · · Score: 2, Insightful

    Dave King, a very common name, but now that I have a modest blog I'm the number 2 Dave King, any one who knows me would be able to add other terms that should make my blog #1, so why would I need daveking.name?
    -Peace
    Dave

    --
    Free as in "the Truth shall set you..."
  34. Not your typical TLD by Skwidd · · Score: 3, Insightful

    The .name registry has some unique features:
    - Customers register 3rd level names (ie: firstname.lastname.name)
    - They charge an additional annual fee to have access to the corresponding e-mail address (firstname@lastname.name)
    - Customers can't use the DNS services that they use for 'real' domain names

    The dotName people had some lofty ambitions when the registry was created. They were hoping that their names would become the standard for unique ids over all kinds of communications -- they'd point to your website, e-mail, cell phone, etc. This sounds like a reasonable idea (a unique communications id), but names are not unique enough...

    Is anyone familiar with any similar (but ideally smarter) efforts?

  35. How about some *sensible* TLDs? by Sheriff+Fatman · · Score: 3, Insightful

    I must admit, I'm not surprised to see .name going tits-up, and I'll be surprised to see how .me.uk plays out over the next year or two. I think this whole notion of trying to cater to individuals is pretty well doomed - there's always going to be too many people with the same name, and they're going to end up as the exclusive preserves of the rich and vain people who happened to get there first. If they really want to sell domains to individuals, give them a bit of character... hands up anyone who wants their own .geek domain?

    On a more general note, I may be missing something *really* significant, but I really think that the internet DNS system suffers heavily from piss-poor management. As it stands, we've got all these fairly uninspiring TLDs - .museum, .aero. .info, the list goes on. I can't believe any commercial organisation are going to go for a .biz or a .info domain without trying to get the .com as well. One of my clients provides information publishing services to the media industry, and they're now buying .com, .co.uk, .biz and .info for every domain they register - not 'cos it's bringing them any extra revenue, but because they're worried about cybersquatters and competitors trading on their brand.

    Added to this, I really don't think ICANN are doing a particularly good job setting up the 'new' TLDs. I've said this before on /., but why the hell isn't there a .movie TLD? Every mainstream film that's released these days has an official website with a fat marketing budget behind it. Movies tend to have short, easily memorable name, and - more importantly - they're almost always unique names, to avoid people confusing one movie with another. Since films don't really depend on their internet presence for revenue the way many companies do, they'd probably be a lot more receptive to using something other than .com at the end. As long as the registration process was vetted the same way as .edu or .ac.uk, you'd rapidly create a system where a .movie site was guaranteed to be the 'real deal', leaving the fanboys to fight over www.starwarsepisode3.com. I'm sure there's numerous other candidates - .game, .book, .show, maybe .band or .music or somesuch. Certainly none of them can be any worse than .museum - do a Google search for 'museum', and see how many pages of results you have to go through to find a .museum TLD. I got bored after about a hundred results.

    .sex and .xxx offer possibilities, too. It can't be that hard for an ISP or hosting company to insist that their customers use a specific TLD for pornographic sites. All concerned parents have to do is block access to .sex and voila! they can sleep at night believing their kiddies are safe from the child-eating internet porn monsters.

    At the end of the day, if ICANN want to provide TLDs as a service, they've got to accept that no-one's going to get rich, and if they want to get rich, they should be identifying their potential markets just like any other business and working to meet the needs of those markets. TLDs like .name and .aero just seem like a waste of everybody's time and bandwidth.

    --
    -- Open Source: It's mad, but you don't have to work here to help.