News for hackers. Stuff that matters.

A comment on Chrome 68 will mark all HTTP sites as “not secure”. Parent comment

Re:Chrome 68 will mark all HTTP sites as “not secure” by degenerate on Thursday February 08, 2018 @09:02PM (#16337318)
I browse a popular gaming forum that has not implemented HTTPS. Chatting with the admin, the reason is simple: Ads.

We can definitely blame the ad networks. Some have switched, but many won't work on https, and websites relying on ad revenue must stay with HTTP or make less money with HTTPS-friendly ad networks.

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by lern_too_spel on Thursday February 08, 2018 @11:22PM (#16337870)
Those shady ad networks are going to get blocked by Chrome anyway, even without the HTTPS warning. Good riddance.
[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by p49k on Thursday February 08, 2018 @11:41PM (#16337933)
This hasn’t been true for at least a year. There is zero difference in ad revenue for HTTP vs HTTPS now. Join any major online community for publishers and ask anyone if you don’t believe me.
[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by mattacular on Thursday February 08, 2018 @09:17PM (#16337397)
Genuinely curious what kind of ads network/system you use that is not fully HTTPS compliant by now?
[ Parent | on HN ]