Hacker News Reader

Comment by Klathmon | Hacker News Reader

It's a chicken-and-egg problem, but it's starting to improve.

Honestly if google really wanted to push this, they would do something to penalize http only ads. That would really pressure advertisers to upgrade or lose.

View on HN

Chrome 51 changelog:

* Images served over unencrypted connections will have 50% of their pixels randomly scrambled.

Why don't ad networks care about HTTPS? It would increase the number of potential sites that can show their ads, make it more difficult for ISPs to block their ads, and allow browsers to load their ads over HTTP/2.

HTTPS requires additional round trips, so slows things down and tends to reduce revenue by a non-trivial amount.

Really? We added HTTPS to a number of ad-ridden sites and found no noticeable impact to end user page load times, page views or ad revenue.

If slow ads were a problem, why are ad networks so damn slow? I frequently see ads taking 10–20 seconds to load on major news sites. Serving fast ads would mean more viewing time, yet that doesn't seem to be a priority for anyone.

"On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10 KB of memory per connection and less than 2% of network overhead. Many people believe that SSL/TLS takes a lot of CPU time and we hope the preceding numbers will help to dispel that."

https://istlsfastyet.com/

It's your privacy not theirs. And they have to pay the increased costs for HTTPS including complexity (key management, etc).

Reply on news.ycombinator.com