Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Announces .new Domain Availability

whats.new

Post reply on HN
Print view View original

111–120 of 166 posts

Re: Google Announces .new Domain Availability

#111

Post by DJHenk »

sdan wrote: post #31

Been using https://docs.new for the past 2-3 months. It's absolutely game-changing as I'm writing a bunch of stories and need to iterate fast and recompile my thoughts just by typing in 8 characters.

> It's absolutely game-changing as I'm writing a bunch of stories and need to iterate fast and recompile my thoughts just by typing in 8 characters.

Is it? Or are you being sarcastic? Every word processor/text editor that has ever existed on this planet has a shortcut for that. Every phone that is internet connected has a notes app only one click away and the option to 'share' whatever you wrote.

These cloud tools have only one appeal, easy synchronization, and for the rest a big list of drawbacks. As this 'revolutionary' (but still worse) functionality demonstrates.

Re: Google Announces .new Domain Availability

#112

Post by jannes »

nullify88 wrote: post #75
AdrienLemaire wrote: post #42

I'm a bit confused. Are these domains only usable as web redirects? Or is it just that the examples shown are used as such, but we can use the domain as any other one? I wonder how having multiple entries to the same page will affect page ranking. Looking up gist.new, I wonder why there are 2 requests done: 307 Internal Redirect 301 Moved Permanently Before getting the 200 request to https://gist.github.com/ .

Due to HSTS (It maybe preloaded in your browser), the browser internally redirects http://gist.new to https://gist.new . And then receives a 301 from the web server (which is cacheable) to redirect you to your final destination. Edit: It is ( https://hstspreload.org/?domain=gist.new )

In fact, the entire .new TLD is preloaded: https://hstspreload.org/?domain=new

Re: Google Announces .new Domain Availability

#113

Post by philsnow »

jianglai wrote: post #51
tpmx wrote: post #34

Earlier quoted context omitted.

If you have a both a personal gmail account and a for-work "google for business" account - the shortcut will take you to whatever account you signed into first . If you attempt to switch to a different account after accessing https://docs.new/ , that will trigger an "ask for permission to access document" dialog. Not awesome. (AFAIK, the only way to fix this is to sign out and then log back in, in the "correct" order…

You can try docs.new/1 and docs.new/2.

multilogin just won't go away, will it?

Re: Google Announces .new Domain Availability

#114

Post by philsnow »

nullify88 wrote: post #75
AdrienLemaire wrote: post #42

I'm a bit confused. Are these domains only usable as web redirects? Or is it just that the examples shown are used as such, but we can use the domain as any other one? I wonder how having multiple entries to the same page will affect page ranking. Looking up gist.new, I wonder why there are 2 requests done: 307 Internal Redirect 301 Moved Permanently Before getting the 200 request to https://gist.github.com/ .

Due to HSTS (It maybe preloaded in your browser), the browser internally redirects http://gist.new to https://gist.new . And then receives a 301 from the web server (which is cacheable) to redirect you to your final destination. Edit: It is ( https://hstspreload.org/?domain=gist.new )

AFAIK google is doing this (HSTS preloading the entire gTLD) for many gTLDs they own, including .app

Re: Google Announces .new Domain Availability

#115

Post by eloisant »

Double_a_92 wrote: post #94
tobltobs wrote: post #92

Earlier quoted context omitted.

> 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 i…

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.

Re: Google Announces .new Domain Availability

#116

Post by tadasv »

derefr wrote: post #19
tadasv wrote: post #2

Why do we need this?

Why would TLDs need to be created based on need? What’s wrong with a company making a TLD as a whimsical cute idea (and still expecting to be profitable doing so, because whimsical people will go along with it)?

I'm not necessarily talking about the TLD. This is more like a "service" that's controlled by google and certain rules are enforced to those who hold the domain.

This makes very little sense to me. I get that it's nice to have a short domain that points to some action. But why do you need a completely separate namespace for this?

Re: Google Announces .new Domain Availability

#117

Post by Double_a_92 »

eloisant wrote: post #115
Double_a_92 wrote: post #94

Earlier quoted context omitted.

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.

Re: Google Announces .new Domain Availability

#118

Post by iainmerrick »

grenoire wrote: post #13

There's a requirements list, by the way: "That means that all .new domains registrations must: - Be used for action generation or online content creation; - Take the user directly into the action generation or content creation flow; - Resolve to the action within 100 days of registration;* and - Allow Google Registry to verify compliance at no cost."

Certainly sounds like an analytics goldmine.
Post reply on HN