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

Google .dev domain early access

domains.google

Post reply on HN
Print view View original

321–330 of 475 posts

Re: Google .dev domain early access

#321

Post by reaperducer »

dehrmann wrote: post #203

When in doubt, racketeer. I've been annoyed by how Google uses Adwords for a while; suppose you're company in a competitive, undifferentiated space. I just searched for "enterprise rental cars," and the first thing below the search box, an ad, was for getaround.com. The second was an ad for Enterprise, the third was the organic result for Enterprise. Google is effectively telling these companies "You wouldn't want so…

They're inventing the demand for this TLD, then telling developers to pay up if they don't want someone to take their name.

For a lot of developers the demand was already there because they had their local virtual hosts on .dev. It wasn’t standard, but it was extremely common.

Then one day Google announced that it owns .dev and all the developers had to move their development domains to a different imaginary TLD or .example since Chrome would no longer let them test web sites on their development environments.

I am a developer. I will not pay Google or anyone else to use .dev simply because I have learned that Google can not be trusted. What prevents Google from taking .dev back in-house one random day and kicking everyone’s web sites to the curb? Absolutely nothing. Because you don’t own the domain. You only rent it.

I keep my development and testing on locally routed .dev and simply don’t use Chrome. Fortunately the people who sign my paychecks only care about Safari. Not everyone has that luxury, but I do, so I will make this minuscule stand that Google will never know or care about because an algorithm cannot know or care.

Re: Google .dev domain early access

#322

Post by [deleted] »

ldiracdelta wrote: post #285
CydeWeys wrote: post #254

Earlier quoted context omitted.

Hi. I'm the Tech Lead of Google Registry, the team that is launching .dev (not to be confused with the linked Google Domains, which is one of many registrars selling .dev domains to end users). You'll be glad to know that TLDs can't simply be discontinued like other products might be. ICANN doesn't allow it. The procedures in place preventing a live TLD from shutting down are called EBERO; more details here: https://…

If I register a domain, can google boot me off it at a later year if they don't like my politics? Or do I own the domain with the continuing option to re-register it or transfer to another domain registrar? Does google ultimately own the domains and simply lease them to me with no guaranteed option to continue?

[deleted]

Re: Google .dev domain early access

#323

Post by reaperducer »

solatic wrote: post #172
pluc wrote: post #12

The .dev TLD worked fine before it was bought. Now we have to use .test or .local. I don't get what Google thinks they'll get out of sponsoring putting sites under development online.

Why do you have to use either one of those? If you're already running your own internal DNS servers (to serve .dev, .test, etc.) , then just buy a domain for your org for internal use (e.g. " -internal. " or " -private. ", or if your company is " .com" then purchasing " .net" or similar), split-horizon so that queries from the Internet direct to some CDN-hosted static page saying "nothing to see here, internal use on…

Why do you have to use either one of those?

I’m not the OP, but I’m in the same boat.

Not every development environment, company, and set of IT/security policies are the same as yours. Just because you cannot envision the problem doesn’t mean the problem doesn’t exist.

Re: Google .dev domain early access

#324

Post by CydeWeys »

icebraining wrote: post #165
jasonbarone wrote: post #152

Earlier quoted context omitted.

Hmm, this definitely isn't the case for .app. There are numerous tiers of pricing as of right now. Google categorized specific names as "Premium", which you can see when searching for a lot of .app domains. These Premium domains vary in both initial purchase price AND the yearly renewal. One of my examples is in this thread. Purchase price was around $1000, yearly renewal is $280. Other names are even higher...

Ah, yes, the (c) clause says they can charge you more if you agreed to it "at the time of the initial registration", but not after you have invested in the domain. But I suggest people read the whole article themselves, I have no industry expertise.

Premium names are common across the domain industry. Different registries handle them differently (some have an up-front cost whereas others like us use annually recurring), but the registrar you're using should be making it very clear what costs you're signing up for during the registration flow.

Re: Google .dev domain early access

#325

Post by reaperducer »

Spivak wrote: post #214
sascha_sl wrote: post #49

Earlier quoted context omitted.

Yeah sure takes one minute, one minute of wondering if you really wanna bash your head against a wall getting openssl to spit out an X509 cert and then some.

Or use any of the million utilities for setting up a machine-local CA. mkcert is one.

You mean wait six to eight months for the IT security department in another division of the company in another state to -maybe- approve my cert request.

Not all web development is three guys on Linux laptops at WeWork.

Re: Google .dev domain early access

#326

Post by opportune »

I feel like if they're going to force https on .dev domains they should just bundle certs with the domain itself. I like https as much as the next guy but it's simply not necessary in many types of websites (e.g. a website with documentation and third party binary links), and they're not making it as painless as it could be to comply with their own rules

Re: Google .dev domain early access

#327

Post by CydeWeys »

jasonbarone wrote: post #142
tedmiston wrote: post #123

Earlier quoted context omitted.

Are you saying the registry can arbitrarily change the .app domain renewal price without control, or that they can charge a different renewal price for different .app domains? I've experienced weird price fluctuations with .io domain renewals in the past, but haven't owned one in a few years.

According to registrars, yes. So for example, let's say I paid $1000 for a premium .app last year when they were released. Renewal price is marked for something like $280/yr, which I didn't expect, because I thought the premium pricing was an initial purchase price only. I thought the renewal price was standard .app renewal rates. When I called to clarify with a few registrars, they said that this premium price ($280…

What registrar did you use? They should have made it very clear during the checkout flow what the annually recurring charge was. Can you try it again now with persona.app (another premium) and post a screenshot of what exactly they're displaying?

Re: Google .dev domain early access

#328

Post by JulienSchmidt »

kortilla wrote: post #316
mhaberl wrote: post #292

Earlier quoted context omitted.

Let's Encrypt certs are valid for 90 days. There are 2 reasons: 1. To limit damage from key compromise and mis-issuance 2. To encourage automation. What is the issue with running the certbot on your server? It's not like you have to run it manually. Here are official reasons: https://letsencrypt.org/2015/11/09/why-90-days.html P.S. Wildcard certs are available for almost a year now: https://community.letsencrypt.org/…

The issue might be executing 3rd party code on a server.

ACME is an open protocol (and very soon it will be an IETF Internet Standard too). There are many alternative implementations. Just find one you trust. We actually did our own DNS-based implementation for our infrastructure.

Re: Google .dev domain early access

#329

Post by jfim »

r3bl wrote: post #310
jonathankoren wrote: post #252

Earlier quoted context omitted.

Compare and contrast whitehouse.gov and whitehouse.com

A company owning whitehouse.com and a government entity owning whitehouse.gov? I'd call that working as intended.

The .com used to be a porn website, in the 90s. That might have been working as intended, but has surprised quite a few people.

Re: Google .dev domain early access

#330

Post by forty »

userbinator wrote: post #265
lazyjones wrote: post #243

Earlier quoted context omitted.

> I bet I could make those accordion sections work in all browsers going back to IE5 without much effort, and use nothing near 120KB of JS to do it. / tags with JS polyfill is all you'd need. https://caniuse.com/#search=summary

Your post shows the big difference in mentality that's partly responsible for why we see so many broken sites --- I haven't ever used those tags before and would just go for plain old DOM style manipulation with JS (which has been around for a very long time), whereas you started with something much newer and took backwards-compatibility as an afterthought to be added on. Your solution requires less initial effort (p…

Why would anyone use an older browser? (Other than IE in old firms - but this is probably becoming rarer and rarer) I guess everyone should upgrade their browser regularly, at least to get security upgrades
Post reply on HN