tld.new
Google Announces .new Domain Availability
121–130 of 166 posts
Re: Google Announces .new Domain Availability
#122I'm sure Amazon's not happy they gave shop.new to eBay.
Shopify is probably more irritated.
Re: Google Announces .new Domain Availability
#123I like the concept behind this but I think the implementation is flawed as it binds the actions to specific providers. For example - repo.new only creates repos on GitHub, playlist.new only creates playlists on Spotify and the music.new thing for OVO Sound is just odd, being specific to a custom cover art generator thing.
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.
Re: Google Announces .new Domain Availability
#124Re: Google Announces .new Domain Availability
#125> That means that all .new domains registrations must: ... 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 am pretty new to this space and I have a couple domains registered for some site ideas I would like to pursue in the future. Do all non-.com domains have these kind of restrictions? I thought they were always recommendations? How and why would Google ever think it is cool to restrict how I use a domain, other than the obvious illegal activities I guess?
Re: Google Announces .new Domain Availability
#126I like the concept behind this but I think the implementation is flawed as it binds the actions to specific providers. For example - repo.new only creates repos on GitHub, playlist.new only creates playlists on Spotify and the music.new thing for OVO Sound is just odd, being specific to a custom cover art generator thing. For me, the better implementation would be where for each "action" there are numerous providers…
I think you might have wires crossed, .new is a domain. So if github buy repo.new then they can host on it. Good names are first come, first served
If Pizzahut bought pizza.new they could host a webservice on there provided the webservice resulted in something new.
Re: Google Announces .new Domain Availability
#127There'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."
I'm wondering how that would work for an online shop. Lets say I went to amazon.new - what should I expect to see? 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...
I am more worried if AWS.new will mean new EC2 instance or new Lambda ️
Re: Google Announces .new Domain Availability
#128> That means that all .new domains registrations must: ... 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.
Because I can't buy pizza.com but now I have a shot at pizza.new I guess. Some companies are willing to jump through hoops if it gets them a good domain
Re: Google Announces .new Domain Availability
#129The registration site had better be at Https://new.new
That domain appears to not be registered
Re: Google Announces .new Domain Availability
#130I like the concept behind this but I think the implementation is flawed as it binds the actions to specific providers. For example - repo.new only creates repos on GitHub, playlist.new only creates playlists on Spotify and the music.new thing for OVO Sound is just odd, being specific to a custom cover art generator thing. For me, the better implementation would be where for each "action" there are numerous providers…
I think you might have wires crossed, .new is a domain. So if github buy repo.new then they can host on it. Good names are first come, first served If Pizzahut bought pizza.new they could host a webservice on there provided the webservice resulted in something new.
Yeah I get that, but rather than Google opening it up for open registration and having the usual domain land grab, they could have created domains for each action and allow service providers to register intents in their services for each action. It's going to make discovery of actions much harder if there are different actions for different providers. It will also mean the usefulness of the pattern will be limited based on the services I choose to use.
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.