311–320 of 475 posts
Earlier quoted context omitted.
Well that's nice. But that mean you'll have to manually buy, upgrade install and test them. I have better things to do.
Takes about 5 minutes of time. It really isn't a big deal.
Earlier quoted context omitted.
The trend across the gTLD industry has been one of decreasing prices, not increasing prices. I'm not sure what you're referring to?
The trend in browsers is being precise about standards and yet only yesterday google took an existing standard and tried to corrupt it. I'm not trying to be snarky and thanks foe answering questions but this particular comment was a non-answer.
Earlier quoted context omitted.
i guess he is talking about the premium domains: > During both the Early Access Program and General Availability, there is a $12/year cost for .dev domains. Annual fees may vary for Premium domains.
"Premium" domains are resold domains. The prices are typically dictated by the person holding them.
Domains being sold by resellers are something different entirely, but yeah, some registrars that participate in reseller networks may lump those in as "premium" as well, which is confusing. Those prices tend to be one-time acquisition costs.
> You can purchase an SSL certificate through one of our web partners or a Certificate Authority. Read this article to learn more. Really? No mention of Lets Encrypt? Does anyone still buy certificates nowadays, especially for dev sites?
Of course they do. Let's Encrypt provides DV (Domain Validation). Not OV (Organization Validation). Obviously .dev is intended for software development and most domains there would probably be using DV only so this might not apply to it, though.
Earlier quoted context omitted.
I buy them. I don't like paying for them, but I want a certificate I know will just work for years without having to run certbot or one of its clones on my server. Well, that and LE didn't yet allow wildcard certs when I bought mine. They've already dropped their maximum validity from three to two years though, so I'll probably throw in the towel when they further reduce their validity to less than six months.
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/…
Earlier quoted context omitted.
I guess I just don't like multi-billion dollar companies coming in and dictating that I change my workflow for their cash grabs.
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.
120KB of javascript and still the accordion doesn't open on OSX Safari.
Also, the navigation and some other parts aren't usable with ad blocker enabled, since there are no non-JS links/anchors. Embarrassing for an entity that once tried to position itself as a supporter of usability and user-friendly web pages.
Earlier quoted context omitted.
You made a fully general argument against anything that Google touches. This isn't useful, because everyone knows that argument already. I'd rather know what Google's track record is specifically having to do with DNS (or fundamental Internet infrastructure).
I think their 8.8.8.8 DNS server has a pretty impressive track record for I think over 10 years. I know many people who changed their dns to 8.8.8.8 when they thought their DNS was shitty. Back in highschool (15yrs ago) pinging a DNS server was something I sometimes did when fixing people's internet, always used 212.142.28.66. No idea why it's still in my head so much later, 8.8.8.8 sure is a lot easier to remember.
Earlier quoted context omitted.
Safari is the new IE8. Every web dev I know bitches about it.
Every bad web dev bitches about it. There's nothing about Safari that makes it "the new IE8". Ironically, the very same HN that bemoans every new thing as "why should devs jump onto this shiny new things, just slow down already" criticises Safari for not jumping onto every new thing.