5 ms·
So the stated use case is for 'performing new actions online: any act that leads to creation can have a quick and memorable .new shortcut associated with it.'
by Cogito 7y ago
So the stated use case is for 'performing new actions online: any act that leads to creation can have a quick and memorable .new shortcut associated with it.'
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!
- derefr 7y agoOther way around: repo.new would redirect to github.com/repositories/new. 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 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.
- Cogito 7y ago> Other way around: repo.new would redirect to github.com/repositories/new. 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?
- derefr 7y agoYou can type it on arbitrary people’s computers, not just your own. Same reason text-editor default shortcuts are important. Not sure about discoverability. Probably they’d just mention the shortcut on the canonical page.
- tasogare 7y agoYou still need to login in your account then, which can took a significant amount of time especially with 2FA. Then the time gain is so marginal it's insignificant.
- derefr 7y agoNot if your app is structured in the way where you can use the create flow in the context of an ephemeral session, and then get asked to log in when you go to save. But yeah, in general, apps don’t do that much, and I wouldn’t see many being pushed to do so just to add such a shortcut. Maybe the case here is where the login will be automatic (e.g. OpenID Connect based)? So, in the case where you’d be using some random workstation, but you happen to be authed to it anyway, by e.g. creating a temporary browser profile and logging into the sync on that. But in that case, the browser sync would still give you access to your bookmarks.... Okay, maybe it was never about browser address bars at all. It seems like a lot of these blurbs on the registrar page are talking about how these things are equivalent to certain API calls you can make to these sites. So maybe the point here is to create memorable API endpoints, such that you can now do something like (not saying this works, but it might): sort -n mydoc.csv | http sheets.new ...where the API endpoint accepts your IO-stream as a POST or PUT request, and returns a URL of the generated document. This would make more sense, because you don’t really have access to your browser’s bookmarks from a terminal; and you might want random agents that you write, which aren’t “logged in” in any particular sense (like a CI bot) to use these shortcuts as well.
- CydeWeys 7y agoYou know how, when you've just recently pushed a new branch to master, and then you go to GitHub, it'll auto-suggest creation of a new pull request with the correct source and destination repos/branches automatically selected, and all you have to do is confirm to send it? That's what I think pr.new should do. I'd definitely use that one a lot.
- nefitty 7y agoYes, this one sounds like a perfect use case. I use docs.new and sheets.new several times a day. It saved me a couple of clicks per action, but subjectively it made so much smoother to stay within Google's ecosystem.
- techslave 7y ago> what does this offer over a bookmark or autocomplete in the address bar? google keyword ownership you don’t necessarily need a bookmark. eg github.com/new is a reasonable enough shortcut
- reaperducer 7y agoI just have no idea why anyone would use a whole .new domain to achieve the stated purpose! Domain squatting is so last decade. The 20's are going to be all about corporate TLD squatting.
- wheelerwj 7y ago100%
- keeganpoppen 7y agogoogle's already got a pretty good head start, too...
- JMTQp8lwXL 7y agoI wonder if CLI commands is a valid use case, e.g: curl -L https://myapp.new https://myapp.new | bash
- ryeights 7y agoBut we already have .sh [1]! [1]: https://en.m.wikipedia.org/wiki/.sh https://en.m.wikipedia.org/wiki/.sh
- huy-nguyen 7y agoBut sh is not a top-level domain.
- growt 7y agoThis is the first sentence of the wikipedia article linked in the comment you responded to: .sh is the Internet country code top-level domain (ccTLD) for Saint Helena
- huy-nguyen 7y agoI meant it's not a "generic top-level domain" like .com or .org so its semantic meaning is the "domain name for websites for St Helena." This is similar to the situation for .io, which was really intended for the British Indian Ocean territory but has been appropriated by the tech industry. I'm in favor of using generic TLDs if at all possible. I believe google also treat generic TLDs differently than country-specific TLDs.
- Already__Taken 7y agodocs.new is pretty convenient