Re:Chrome to force .dev domains to HTTPS via preloaded HSTS
by CydeWeys on Sunday September 17, 2017 @01:29PM
(#15270693)
"If I'm overriding random domains without doing my due diligence, then I get what I deserve."
I mean, that is exactly what is happening here, so it sounds like you get it. We aren't doing things on other people's behalf; HSTS is part of our plans.
I disagree that this is something that Google needs to do on my behalf. If a cybersquatter squats on <my-startup>.dev, I don't consider it broken if I can't access their squat page. If I'm overriding random domains without doing my due diligence, then I get what I deserve (and probably wanted the results anyways). If somebody is spoofing a domain as a method of cyber attacking, the domain owner should have had HSTS if they had dignificant digital assets and they would already be using a non .dev domain.