The image proxy-related change reminds me: CloudFlare and Brave use our rules to do automatic rewriting of requests to upgrade from HTTP to HTTPS and keep users safer. (The first item on our architecture roadmap is actually "signed rulesets", a feature to allow EFF to sign rulesets and thus allow users and downstreams to easily download rulesets on their own, outside the extension's updating mechanisms.) Would Dreamwidth be interested in getting https_url to also draw from that set of rewrite rules?
YAY! More HTTPS!
I'm currently one of the people working on the EFF's browser extension HTTPS Everywhere. I see
The image proxy-related change reminds me: CloudFlare and Brave use our rules to do automatic rewriting of requests to upgrade from HTTP to HTTPS and keep users safer. (The first item on our architecture roadmap is actually "signed rulesets", a feature to allow EFF to sign rulesets and thus allow users and downstreams to easily download rulesets on their own, outside the extension's updating mechanisms.) Would Dreamwidth be interested in getting https_url to also draw from that set of rewrite rules?
Someday, HSTS! (In v2 or later, I infer.)
Thanks and yay again!