I think there'd be a bit less panic in the comments if the title/headline reflected that the change (as I understand it) applies cross-origin and cross-scheme (

I think there'd be a bit less panic in the comments if the title/headline reflected that the change (as I understand it) applies cross-origin and cross-scheme (http > tls). So if you're preventing hot-linking of assets, this should not affect you (or; you have some control over it via policy): > this new stricter referrer policy will not only trim information for requests going from HTTPS to HTTP, but will also trim path and query information for all cross-origin requests. Seems like a fairly balanced way to protect privacy along with preserving utility?