This latest flash of "chrome marks http as insecure" news seems very premature. It's an experimental feature behind a flag and as far as I can see there's nowhe

This latest flash of "chrome marks http as insecure" news seems very premature. It's an experimental feature behind a flag and as far as I can see there's nowhere any indication that this will hit average users any time soon. Which is a bit disappointing. Chrome and later Mozilla announced years ago that they'd do this, yet as long as it's an announcement for some undefined point in the far future it doesn't create any pressure to the ecosystem to become more https friendly. I'm saying this as someone who regularly works for publications that can't use HTTPS, because Ad-networks don't care. I'd really wish Google/Mozilla make their plans to mark HTTP as insecure true.