Huh. "drop" is its own antonym here.

"Google to Drop Eight (New) gTLDs" = Google adding eight gTLDs

"Google to Drop Eight (Old) gTLDs" = Google no longer supporting eight gTLDs.

I really dislike the use of "drop" in headlines like this, it's so ambiguous.

To add to the confusion, "new gGTLD" can mean any gTLD that was introduced after 2011:

https://newgtlds.icann.org/en/about/program

> Both gTLDs [.zip and .mov] match popular file extensions

I wonder how Slack will handle this, or any other tool where both filenames and (auto-hyperlinked) hostnames get passed around. Honestly, the new domains these will enable don’t feel worth the added confusion from overloading the extensions.

This should be handled in the URI scheme. Files have file:// and web has http:// or https://

There’s also a UI difference. I don’t use Slack, but files tend to be shared using a file picker/ drag & drop whereas websites are shared as URLs.

I've been waiting forever to buy a .ing domain from Google as my last name ends in those letters. I literally want to give them my money and they won't let me. I did end up purchasing a .ng domain for my personal website, but I'm not super keen on having it tied to the country of Nigeria.

How often does Google release these new domains? I know that .ing was delegated to them in 2014... why are they allowed to control these domains if they never release them?

Someone will definitely get 42.zip or 42kb.zip just to host a “zip bomb as a service”.

On a more serious note, new gTLDs are so spammy, and “.zip” as others have mentioned will surely lead to some surprises somewhere.

These are going to be ripe for abuse. I don't think there should be any TLDs shadowing popular file extensions.

.zip feels like it might get annoying for auto-linking in text messages, but this is a great set of actually-generic ones.

great, more stuff to blackhole in piHole.

{g,}TLDs domains are administered for-profit in a cancer of exclusivity, like Putin and his oligarchs replaced by ICANN and megacorps.