Live data from Hacker News

First .dev Domains Go Live

blog.google

201–210 of 227 posts

Re: First .dev Domains Go Live

#201

Earlier quoted context omitted.

But does the money come from Microsoft or from GitHub? In a lot of the large companies I've worked, money is siloed from one operating unit to the next. They would send bills between units and sometimes even departments. The larger the company, the more common this seemed. It's not one giant piggy bank.

Does it really matter? Surely $11k is still a tiny amount for GitHub.

~One month salary for a senior dev.

Re: First .dev Domains Go Live

#202
post #162

Earlier quoted context omitted.

It's not. You can make your own DNS server and sell records to anyone you want. You just have to convince users to type in your address instead of 8.8.8.8.

Realistically, how could a project be setup around this? I mean, how do we get everyday normal people to use it? Its been attempted before (namecoin etc)...but maybe some advantage could be given to make it more attractive.

The current state of things are OK enough that it's not worth it to normal people to make the switch. If that time ever comes, people will do so.

Re: First .dev Domains Go Live

#203

Earlier quoted context omitted.

The rich get first pick. How very capitalist.

The auction isn't designed to be fair for all, it's designed to allocate domains efficiently (in the economic sense). Mr. mslev does not consider [hisfirstname].dev to be worth $11k, so he will not buy it yet. But someone else might consider [hisfirstname].dev to be worth $11k, so they will buy it. However, if nobody else values [hisfirstname].dev much, then Mr. mslev will buy it when it costs $12 (or earlier, if he…

Exactly. The alternative of not doing a Dutch auction at launch is much worst; valuable names end up in the hands of squatters who are perfectly happy to sit on many names that remain unused so long as they can sell a few at exorbitant prices. The average non-squatter registrant is better off with EAP and premium prices, as the prices you pay during EAP are lower than what a squatter would try to get out of you for the same domain.

Re: First .dev Domains Go Live

#205
post #89
post #52

Earlier quoted context omitted.

Probably the former as it doesn’t require as much aggrandizement. I wonder whether a different approach would work. Instead of basing TLD name spacing on nebulous terms (com,net,org,io,edu,etc) create a naming system that better reflects the real world. The abstracted terms lead to clashing. So addressing actually reflects physical addressing. There’s only ever going to be one company at Apple’s corporate address. No…

We could just give everyone who wants a domain a UUID. My site could be 'uuid://09953e01-8164-4e40-8504-ed5507b50b03'. This seems to solve all of your complaints. No clashing, reflects the real world (names are all meaningless is reality, and physical locations are nebulous). > There’s only ever going to be one company at Apple’s corporate address. On the other hand, there are corporate addresses that have many compa…

I'd be legit on board with that, I really just want a stable identifier that's independent of routing information or network or whatever.

Re: First .dev Domains Go Live

#206
post #183

Earlier quoted context omitted.

Oh, interesting, yes this is "mauritius" in Spanish a not so common name. I didn't know this, thank you for pointing it out. I guess that list is recent as mauricio.com and mauricio.co belongs to regular people and are currently working. Do you happen to have a link to said list? A quick googling returned nothing relevant for me.

I believe item #3 on this page is relevant: https://www.icann.org/resources/country-territory-names#rese...

Yeah that's it, it's Mauritius in Spanish apparently.

ICANN definitely went overboard on these required reservations, but of course we have no choice but to comply.

Re: First .dev Domains Go Live

#207
post #200
post #18

Earlier quoted context omitted.

The `.test` and `.localhost` TLDs are already reserved for such purposes: https://tools.ietf.org/html/rfc2606

Interesting. Because my /etc/hosts file had the following as a default: 127.0.0.1 localhost.localdomain localhost ::1 localhost.localdomain localhost I thought it was `.localdomain` that was reserved.

I really thought so too! But I can't find any reference for it.

Re: First .dev Domains Go Live

#208
post #104

Earlier quoted context omitted.

Try to register through Gandi. They give you options that decrease in price all the way down to ~$16 -- that's the "get it when it GAs" price. If someone scoops it up before you, you're refunded. Otherwise, it's yours. I managed to get .dev, and it's a somewhat common last name, for $133.50 on the "GA" pricing. I expect someone will grab it before then. But if not...

It'll be 12$ on get.dev once it hits GA.

I looked up [firstname].dev and it says even in GA it will be $360/yr because it is a premium name.

Re: First .dev Domains Go Live

#210
post #196

Earlier quoted context omitted.

The rich get first pick. How very capitalist.

It's much more fair this way. If domains were cheap right away, bots would buy all them up. This gives people the chance to buy a domain- this round is more for businesses, but future rounds in the hundred of dollars will be better for the average person.

How can it be called fair at all when only the rich get first pick?

> If domains were cheap right away, bots would buy all them up.

No. Bots would buy them all up if bots were allowed to buy them all up. It's laughably easy to prevent bots from buying domain names if you don't want bots to buy domain names.

> This gives people the chance to buy a domain

This gives rich people/businesses the chance to buy a domain.

> future rounds in the hundred of dollars will be better for the average person.

After the rich have had their pick. Again, I don't see how you can with a straight face call this fair.

Here's a suggestion: Offer domains to all humans who can pay a reasonable non-refundable application fee. Block bots. When a domain receives more than one offer, randomly assign it to an applicant. Block domain transfers permanently to prevent squatters. Let any domain that isn't renewed fall back into the pool and become available (again to a randomly assigned new owner).

I'm sure there are pitfalls doing it this way, but it took me a minute to come up with that. A few hours of thought, some robust debate, and I'm certain we can come up with a fairer way to assign domain names.

Post reply on HN