Hiding mixed content warnings (like Chrome did last year http://arstechnica.com/information-technology/2015/10/chrome-finally-kills-off-the-http-https-mixed-con

Hiding mixed content warnings (like Chrome did last year http://arstechnica.com/information-technology/2015/10/chrome-finally-kills-off-the-http-https-mixed-content-warning/ http://arstechnica.com/information-technology/2015/10/chrome...) would probably also really help some sites with SSL everywhere. On sites that allow users to embed things like images (forums, comments, etc), in order to avoid mixed content warnings or interstitial confirmation dialogs, you either have to pipe everything through an SSL proxy, or severely limit the types of things users can embed.