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.
The intent of .new is when you know you want to perform a specific action (like write a new doc), you type in the first few characters of the related .new domain name, let the browser autocomplete do the rest, and now you've already got the new thing and are working on it instead of having been deposited at the home page of the site in the question and then have to navigate through the UI to make the new thing yourself.
https://newgtlds.icann.org/en/announcements-and-media/announ...
Obviously since it's Google, they are going to show off all the features first-hand.
So it's expecting users to go to a different website to perform one specific action, and then return to the original website?
If I'm on github.com, click the new repo button, and get redirected to 'repo.new' I'm assuming the website has been hacked.
If I want to create a new repo on github the last thing I'm going to think is 'oh yeah, I'll just type repo.new and that will be super easy' - I'll go to github.com and click the new repo button.
I just have no idea why anyone would use a whole .new domain to achieve the stated purpose!
Imagine a webapp whose landing view page is very heavy-to-load because it’s a view of your library of documents. Like, say, Google Docs. Now imagine there’s a thing you can type instead of docs.google.com (i.e. https://docs.new) that’ll let you skip past that library view, straight to a blank new document view, so you can immediately start typing. That’s the idea here.
Look at that!, it does redirect to github.com/new/
I guess that will be useful for some people? It feels a little bit like mystery meat though; how do I discover these super useful shortcuts?
If I am someone who would benefit from learning a quick-to-type shortcut for performing an action, say because I create these things all the time, what does this offer over a bookmark or autocomplete in the address bar?
Domain squatting is so last decade. The 20's are going to be all about corporate TLD squatting.
curl -L https://myapp.new | bash
I don't get why anyone would want this over a regular domain with which they can do whatever they want with no restrictions.
It's just another way for Google to control and have a say over other people's businesses. For sure we'll see again posts about people having had their product destroyed because Google cut them off with no way to appeal.
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.
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's real HALLOWEEN for me tbh.
"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."
Maybe a new empty shopping cart?
Or a list of new products that have just been added to the store?
I think new products would be most intuitive for a shop.new domain...
Plus, you'd have a collision problem. What if one company has foobar.com and another has foobar.net, and they both collect data? (Imagine they're in completely different industries and the term itself is fairly generic, so there's no possibility of a trademark dispute.) They can't both get the ".delete" version of their second-level label.
(I realize I'm probably overthinking this.)
So you'd thus have foobar.com.delete and foobar.net.delete, no collisions.
Not saying it's great, but it'd work.
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.)
(This is on a Windows desktop running Chrome.)
On chrome desktop, I have separate profiles for work and home so nothing is intermingled.
now i can just do ctrl+t->docs.new->start typing words on a page
new.github.repo
It makes more sense and sounds better in most languages too
Although from the point of view of HTTP we already have verbs for that. It should really be
POST github/repo
Or maybe in user friendly display:
new github/repo
I guess maybe usa.github and in.github can be different domains because different organizations may have same name in diff countries
Treating a TLD as a verb is just silly. It comes at the end of the sentence...
Also it encourages stuff like repo.new to be owned by only one company - github - but what about atlassian butbucket etc?
Better to just have decreasing specificity. Like you have after the slash!
- new `github/repo` will open a browser tab for new github repo
- new `text` <document-name> will create a new txt document
can be extended by adding more definitions
Yes, ending a sentence in English with a verb is definitely something that you never do. Can you imagine how ridiculous that'd be?!
Fine — it’s not a verb, it’s an adjective after a noun.
YES. Give HTTP verbs a place in the URL bar. That'd be huge.
I'd kill clin.sucks as a mail domain.
If you're .old enough, you might want to register coke.new.
Hopefully, if enough of these tlds are around, there's too much real estate for it all to be squated on. Although I have a feeling it's still going to be a .com world for a long time.
Edit to add: the terms are pretty weird on this. I would not want to build my brand around a domain thag Google could take away capriciously because they didn't think you followed their terms enough.
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?
More than anything, I fear that it will teach my parents that domains can look like anything, so that link in the email is probably fine.
You get a fair bit of defense for it around here, but ultimatly it's just rent seeking. Keeping younger generations out from having decent name just because you arrived earlier doesn't really promote a healthy web, nor provide real economic value.
Of course, most squatters would respond "I was planning on using that domain", so it's easier politically to just flood us with new ones.
My company name is squatted on several tlds ( by different people, obviously no intention to use them ). The .com owner wanted to charge me $40,000 or $1000 p/m. Fuck that. I used an alt tld.
The funny part is ads having to add the "www." part, again, instead of just "word.[recognizableTLD]".
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/.
Edit: It is (https://hstspreload.org/?domain=gist.new)
For me, the better implementation would be where for each "action" there are numerous providers and at a user level you could define which one you want to use. So user A goes to repo.new and gets redirected to GitHub, user B goes to GitLab, user C to Bitbucket and so on. The first time you go to the action you're prompted to select which service you want to use by default and from then on you go straight through.
If Pizzahut bought pizza.new they could host a webservice on there provided the webservice resulted in something new.
In your example - if I prefer Domino's to Pizza Hut, what do I go to? I need to go to pizza.new to discover that it's linked to Pizza Hut and then try to figure out what Domino's action might be. In the end I'll just end up going to the main site instead. I think the value of this concept is completely nullified by binding the actions/domains to specific providers.
I just wish it could convert files.
Probably Microsoft didn't get around to re-issuing the cert yet...
These new TLD's strike me as just a money grab before some people realize a domain name matters FAR less than most people thing.
Maybe I'm just not the target audience but I don't ever see myself typing "gist.new" into my address bar. Anyone who knows what a gist is is going to go to github and if you don't know what a gist is then you aren't going to know to type "gist.new" into the address bar.
On a practical note, if you are gunning for a promotion, setting up "widget.new" would make for a cool demo for management.
This seems like a case of 'the left hand doesn't know what the right hand is doing'.
docs.new doesn't do me any good if I use a competing product to Google Docs. Similarly, I might want to use playlist.new without Spotify.
Sure, these are just domains, but it really sours this weird use of this tld as a "way to do things" that it's set to specific companies' services.
http://repo.new/ goes to github... sorry gitlab - you lose this round.
From a security standpoint, using the _path_ of a trusted domain is still a thousand times more secure and convenient, rather than navigating to another arbitrary domain name with no validation of whether it is affiliated with the domain where you've come from.
If Google push this sort of mechanism, it's opening up a whole load of fraud capabilities! If I'm on gmail and receive a phishing attack email, tricking me into navigating to "gmail.new" which asks for my google password, should I type it into the box? There is a green padlock in the URL so it must be fine.
[[domainSearchCtrl.getMessage('How exciting! {domain} is available.')]]
Giving the .new domain to the dominant company just makes it harder for everyone else to compete with them. Which is probably the point.
Also the price seems a bit high for a TLD :G
This is awful.
re.new k.new si.new
Not much there. I guess you can use phrases:
outwiththeoldinwiththe.new
There is just a lot more possibility with Google's "app" TLD.