https://www.troyhunt.com/life-is-about-to-get-harder-for-websites-without-https/
>The bottom line is this: if you're serving anything over an insecure connection you need to be planning how you're going to go HTTPS by default now. There's a great appetite to go secure by developers themselves too; a few months ago I published a new Pluralsight course on What Every Developer Must Know About HTTPS and it went straight up into the Top 10 in a library of more than 6,000 courses. If you're embarking on the journey to a secure transport layer, that's a great place to start.
>It's taken us a while, but finally we're getting to a "secure by default" web!
What do the agencies know that folks like this don't? If he really cares about security, why isn't there a SINGLE word on javascript?
>>61336749
>HTTPS makes things secure
>but you send all your data to Mozilla and Google anyways in the form of telemetry