3 ms·
HTTPS is definitely good but this is a bit strong handed. Many small devs don't want to deal with the complexity of HTTPS and the extra fees. It's a lot bette
by bcheung 8y ago
HTTPS is definitely good but this is a bit strong handed.
Many small devs don't want to deal with the complexity of HTTPS and the extra fees. It's a lot better with Let's Encrypt but I've talked to non technical people who have shelled out $300/year to their host providers just to have HTTPS and inevitably lots of things break due to hard coded links in their outdated software.
If authentication happens through a 3rd party provider and the there isn't any need for a site to be secure, why force the matter?
Broken sites lead to a massive drop in sales. All because Google thinks it knows best.
If they truly wanted to solve the problem, why don't they offer a proxy, that converts HTTP traffic to HTTPS traffic that gets used in Chrome.
Instead they force people who don't have the technical knowledge that they can get HTTPS for free to pay huge fees and inevitably have their sites broken in the process.