Hacker News Reader

Comment by Already__Taken | Hacker News Reader

This is pretty normal, all registras have usage restrictions. Most are poorly enforced but googles reqs seem pretty reasonable, The problem with all registers is you have very little recourse.

I quite like gsuite but if your only domain is bought as a google TLD on google domains with your gsuite account via google pay with google voice contact details and gmail contacts. God help you.

View on HN

> all registras have usage restrictions.

Sure, but I never saw anything as ambiguous as:

* Be used for action generation or online content creation;

* Take the user directly into the action generation or content creation flow;

* Allow Google Registry to verify compliance at no cost.

That some AI script with a failure quote of ~2% will verify your compliance wont help also.

And the only way to get some human support in those cases is when you manage to get on page 1 of HN with your "crying for help" tweet.

That still seems pretty reasonable. They want ".new" to be seen and used as an interaction element, not as a random TLD. E.g. if twitter would get one, twitter.new would bring you somewhere where you could directly start typing a new tweet.

Well, good luck when your app gets flag by their bot, broken because the .new no longer works, and you can't get a hold of Google to remove you from their blacklist.

Just read all the horror stories about apps on Google Play.

Well that would be a different issue... But their requirements / vision for the .new domain are not unreasonable or ill-intentioned.

Well intention doesn't help you if the execution sucks.

What about "car.new", where you can buy cars? Would that be enough "action generation"?

tesla.new where you can order directly online, yeh probably. That's I reckon exactly the kind of distinction I think they're going for. ford.new would make me go to a dealer so I think they should be able to never get one.

But when you can book an appointment at a ford dealer next to you that would be kind of "action generation".

Or what is when Ford will never get ford.new, is it free to register by anyone?

> Or what is when Ford will never get ford.new, is it free to register by anyone?

Trademark law still exists, this is a solved problem.

Would only apply is the domain is being used with cars. Ford is a common last name.. could be dentist call to action.

As a user I don't think I'd ever go to .new directly. If you've got some other way to get users there from the main site, you might as well use a query string, path, subdomain or some combination of the three.

I'm not a web dev, but I've dabbled a bit over the years. So I guess I could be missing something. I'm sure the right marketing could make this work.

They seem quite different, restrictive, and onerous to me. In particular "registrations must have websites that are both live and compliant within 100 days of registration". You can't register a domain to use later, you have to get something up quickly, something that satisfies Google's vague "action" requirements.

That part is actually positive though - if you want to squat a domain for over 100 days too bad.

And how is that supposed to work in reality if your project takes more then 100 days to build?

start building it locally and then only buy the domain once it's close to complete?

What has the "where you built it" to do with the domain name?

Reply on news.ycombinator.com