> Also does anyone know what the new personalisation features are that they mention being able to offer now HTTPS in place? Not sure what features the NYT is r

> Also does anyone know what the new personalisation features are that they mention being able to offer now HTTPS in place? Not sure what features the NYT is referencing specifically, but Chrome has certain features [like the Geolocation API][1] disabled for pages loaded over HTTP. See [Deprecating Powerful Features on Insecure Origins][2]. [1]: https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only https://developers.google.com/web/updates/2016/04/geolocatio... [2]: https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins https://www.chromium.org/Home/chromium-security/deprecating-...