Sunset Progress for January 2023

[zoracon]

Announcements

• Blog: https://www.eff.org/deeplinks/2021/09/https-actually-everywhere
• Web Page explaining HTTPS Only Mode in browsers: https://www.eff.org/https-everywhere/set-https-default-your-browser
• Extension: https://github.com/EFForg/https-everywhere/releases/tag/2022.5.24
• Repo: https://github.com/EFForg/https-everywhere#readme

Affiliated Websites that will need to be taken down

• https://atlas.eff.org/index.html

• https://www.https-rulesets.org

• https://www.https-rulesets.org/v1/

• https://www.https-rulesets.org/ddg/

• Archived information will still be at https://www.eff.org/https-everywhere.

De-listing in Stores

• https://addons.mozilla.org/
• https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp
• https://microsoftedge.microsoft.com/addons/detail/https-everywhere/fchjpkplmbeeeaaogdbhjbgbknjobohb
• https://addons.opera.com/en/extensions/details/https-everywhere/

Misc.

• Unpin from org repo
• Decomission private key for Chrome signing
• Decomission email list servs:

HTTPS-Everywhere	HTTPS Everywhere Genral
HTTPS-Everywhere-Rules	Rulesets

• Close MM channels

[KOLANICH]

I don't think that sunsetting the extension and delisting it from stores and removing the rulesets is a right move. They are still useful. We still cannot just blindly rewrite http to https. For example rulesets are used to bulk-rewrite links in files. And the non-enforcing mode of the extension is useful when dealing wjth people who just disable the extension wholly if it js in the enforcing mode. Also UX of browser's HTTPS-only mode is poor.

I think the extension and the datasets should not be "sunset".