You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Point out difference b/t HTTPSE and Smart HTTPS in FAQ #7936
Did someone ask this question "in the wild"? I'm wondering who the audience for this question is: security professionals, non-technical activists? There are trivial differences like securecookie, but the difference that really matters is that HTTPS Everywhere rulesets have been curated by people over possibly thousands of hours while Smart HTTPS is just an automated program. How we "sell" HTTPS Everywhere vs an automated program depends on who we're talking to.
@jeremyn yes, there was an inquiry that came in to the info@eff.org email address. That's why I think it would be good to address it. Lots of people complain about the memory usage of the addon, and I think it'd be a good question to address and point out that there's a huge benefit that comes with the memory cost.
btw I just limited the discussion on this issue b/c I mean this to just be a reminder to myself to create a PR for this, I don't want it to get too freewheeling. once we have a PR that can lead to a discussion, I just don't want to forget to do this
@pipboy96 Sorry, the reason I removed the lock is that you locked it from the beginning, without reason for lock (now GitHub allows specifying reason), and that apparently there was no such "complaints" anymore.
I want to actually write a section explaining how both extensions work and what's the problem with S-HTTPS, and why it does not apply to HTTPS Everywhere and EASE mode.
Activity
jeremyn commentedon Dec 21, 2016
Did someone ask this question "in the wild"? I'm wondering who the audience for this question is: security professionals, non-technical activists? There are trivial differences like
securecookie, but the difference that really matters is that HTTPS Everywhere rulesets have been curated by people over possibly thousands of hours while Smart HTTPS is just an automated program. How we "sell" HTTPS Everywhere vs an automated program depends on who we're talking to.jeremyn commentedon Dec 21, 2016
On https://addons.mozilla.org for the HTTPS Everywhere add-on, there's a review that says:
Do we want this FAQ to cover this person's question?
Hainish commentedon Dec 21, 2016
@jeremyn yes, there was an inquiry that came in to the info@eff.org email address. That's why I think it would be good to address it. Lots of people complain about the memory usage of the addon, and I think it'd be a good question to address and point out that there's a huge benefit that comes with the memory cost.
btw I just limited the discussion on this issue b/c I mean this to just be a reminder to myself to create a PR for this, I don't want it to get too freewheeling. once we have a PR that can lead to a discussion, I just don't want to forget to do this
jeremyn commentedon Dec 21, 2016
Sure, that's fine. Please ping me when you submit the pull request.
Hainish commentedon Dec 21, 2016
Will do!
pipboy96 commentedon Mar 28, 2019
Why was this even locked?
Hainish commentedon Mar 28, 2019
This was answered in #7936 (comment).
Please do not undo the actions of repo maintainers without clearing it with them.
pipboy96 commentedon Mar 28, 2019
@pipboy96 Sorry, the reason I removed the lock is that you locked it from the beginning, without reason for lock (now GitHub allows specifying reason), and that apparently there was no such "complaints" anymore.
pipboy96 commentedon Mar 28, 2019
I want to actually write a section explaining how both extensions work and what's the problem with S-HTTPS, and why it does not apply to HTTPS Everywhere and EASE mode.
Hainish commentedon Mar 28, 2019
@pipboy96 that sounds great!