Hacker News new | ask | show | jobs
by x1 5113 days ago
I don't really feel this... I guess this might be a horrible thing to say but "I don't really care".

It costs 100k to get a tld. So if Amazon takes .author then what about .writer? Or what about biographer, columnist, composer, creator, essayist, ghost, ghostwriter, ink slinger, journalist, originator, playwright, poet, producer, prose writer, reporter, scribbler, scribe, scripter, word slinger, wordsmith, work-for-hire, writer?

Is amazon going to take all of them? So what if they do? Does that suddenly invalidate FirstNameLastname.com/net/me/us/co.uk or FirstNameLastnameAuthor.com/net/us/co.uk?

I'm worried about the opposite trend. That is to say Amazon (or any other company) REQUIRING people to buy a certain tld before allowing them to use certain services (want to sell in the apple store you must buy a .apple tld, want to publish a book you must buy a .book tld)

1 comments

Interesting last point there. Ties into what I'm thinking will happen with certain gTLDs, namely that the gTLD will set rules and structure around how that gTLD can be used.

For example, .tel, domains in that namespace all have the same structure by design. I don't believe a .tel registrant can change their DNS in order to do otherwise.

This is a good thing to an extent - DNS for most people is a huge hurdle preventing them from establishing their own online presence, now more so due to IPv6. If new gTLD provide tools to get .author's or .lawyer's presence up and running in an effective and fair way, great.

But overall I am discouraged by this possibility as its a nail in the coffin of the open internet. It's akin to the review process in mobile AppStores, really stating what you can and can't do within the confines of a gTLD. Not something I'm looking forward to becoming comfortable with on the web.