411–420 of 475 posts
Earlier quoted context omitted.
Ask yourself "Do I pay for this Google product?" If the answer is yes, then the product comes with actual support.
They should quote that on the GMail sign up page.
Earlier quoted context omitted.
Who bought it is irrelevant. It could have been released to the public in a similar way to .com and the same issue would remain. The .dev TLD was never reserved for your dev use. If you had been doing it correctly and following the RFC, you wouldn’t have to change anything with your workflow. Now, if they ever release .test for public use then I’ll grab my pitchfork with you.
The fact that it is legal doesn’t make it any less of a PITA though.
Earlier quoted context omitted.
Probably none, going by the track record.
It really depends on the product. E.g. if you buy Google Wifi, you can call them or chat with customer support, etc. If you need help with constructing a web search query, not so much. So, please do not over generalize or compare apples to oranges.
Earlier quoted context omitted.
You may get a kick out of this... Google Support 12:53 PM Thank you for contacting Google Domains. My name is and I'll be happy to assist you. Let me quickly read your notes here. 12:54 PM Hi there 12:54 PM How are you? 12:54 PM Hi. I'm trying to read your website but it's broken in one of the dominant web browsers in the world. 12:54 PM Hi you said that the link https://domains.google/tld/dev/ doesn't work on Safari…
> Hi. I'm trying to read your website but it's broken in one of the dominant web browsers in the world. Don't we all hate reports like this one. "Yeah I know what information you need but my high horse told me to write this crap instead."
Earlier quoted context omitted.
.test, .example, and .invalid are also reserved by the RFC and don't have this problem.
> ".test" is recommended for use in testing of current or new DNS related code. This one looks the safest and least prone to confusion. > ".example" is recommended for use in documentation or as examples. > ".invalid" is intended for use in online construction of domain names that are sure to be invalid and which it is obvious at a glance are invalid. Both of these look problematic from a terminology standpoint, not…
There is a draft RFC to reserve .internal for this purpose, which I think makes a lot of sense.
Earlier quoted context omitted.
Doesn't matter the level of support, the CEO of Cloudflare was involved and still ended up bringing politics into infrastructure.
Who is a good/trustworthy registrar then?
Instead they have implemented a braindead dutch auction-style system that ensures developers will not be represented fairly. The marketing and implementation of this are out of touch and its doubtful this effort will be successful.
Earlier quoted context omitted.
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.
Something tells me it's not actually that much trouble though, and people just like whining about minor inconveniences because it's the internet and they can.