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.
In FAQ, add more info on reaching out to site owners #9467
I think it's perfectly fine for people to write site admins explaining why
HTTPS is important. I don't think we want this as part of the extension
itself (too pushy and seems misplaced) but perhaps somewhere in the FAQ.
It would be nice to clarify the relationship we want with site owners. We've generally been very accommodating to site owners, however my experience with them has usually been that if there is any ambiguity or difficulty, they would prefer that we not include their site in the add-on. This makes sense if you think about it: HTTPS Everywhere can break the experience for users, break ads, and is outside of the site's direct control and requires a technical person's time to work with us to fix problems. They can use HSTS if they want what HTTPS Everywhere does.
We can specify this in the FAQ and perhaps this belongs in CONTRIBUTING.md as well.
Something like:
When reaching out to the site owners, ensure that they themselves are confident of the layout and longevity of their TLS deployment, and prefer to be included in HTTPS Everywhere. Otherwise, the ruleset(s) that are created can be brittle and cause problems for users trying to access the site.
What I really would like to see is a small email template we can use to write to website owners.
Many contributors (myself included) are not native speakers and therefore don't always convey ideas in the most clear and efficient way.
A template explaining why https matters and how eventually it is to going to be mandatory (given Google and Mozilla stance on this) would help a lot with this issue.
On further thought I'm not sure what this issue/proposed FAQ update is for. When I've contacted site owners, it's because I want their help to write a rule because there is something unusual or difficult about their site. An email template wouldn't help with that because each problem is unique.
We don't need to email site owners about why HTTPS is important. The tech people at these sites that we talk to know about HTTPS and why it's important, they want to support it, and they are competent enough to do it. However unless the site is trivially small or was built from the start to support HTTPS, actually deploying HTTPS is complicated by stuff like CDNs, ad networks, analytics, competing business needs, testing requirements etc. Emailing them a beginner's level description of HTTPS when they are already fighting the HTTPS battle with their management and customers will not help.
Also, of course, we are only able to create rulesets for sites because those sites have already gone to the trouble of at least partially supporting HTTPS. We are always building on the work of the site owners.
The tech people at these sites that we talk to know about HTTPS and why it's important, they want to support it, and they are competent enough to do it.
I don't argue with that. But I don't think site owners are necessarily the same people as site developers. You also seem to talk only about "big" websites but those are not the targets I have in mind for this kind of email.
For example, some independent news websites don't support https. It may be because they don't realise that all their traffic is in clear text. The people who run it are not always tech literate. I believe in this case, a short email saying that as a user, you would like to protect your privacy and how https helps with that would be great. Even if they are already aware of the issue, proof that it matters to their users may motivate them to focus more on it.
Then, I agree their tech are surely capable enough to take care of the technical stuff or they can easily seek help. Hence the fact I didn't mention it in my proposed points for a template.
At EFF the canonical resource we've used to explain the importance of HTTPS is our "Encrypting the Web" page: https://www.eff.org/encrypt-the-web
This specifically has a "What you can do as a web site owner" section. I would not assume that any site we're interested in adding coverage for already knows the importance of HTTPS. Often, those offering very sensitive information just haven't thought about offering HTTPS, or don't really know what it provides.
I think an email template would be fine, but definitely linking site owners to the "Encrypting the Web" page is best practice.
Professional site admins would not appreciate random emails with basic HTTPS information and would probably consider it spam from the EFF. Low-tech people who, perhaps, barely managed to follow a tutorial to buy a domain name and set up a WordPress blog on shared hosting, will not know what to do with this information and will have many questions. I'm having trouble picturing a webmaster@example.com in 2017 who is both low-tech enough to need basic information, but high-tech enough to figure the rest out on their own.
The EFF does good work in raising general awareness and changing the public mindset about encryption. This makes it easier for players like Google and Mozilla to make HTTPS the default and plain HTTP be seen as deficient. This is not the same thing as directly emailing specific site owners/admins.
My own take is that nobody should email a site owner/admin trying to convince them to use HTTPS unless that person is willing to patiently answer their questions. If they send the email out claiming any association with the EFF at all, even as a volunteer, then they should be willing to answer those questions for free.
Also keep in mind that even tiny businesses and nonprofits will have technical people involved in making the websites, often as part-time help from a consulting agency.
I have a hard time trying to convince myself that the level of email traffic generated by the proportion of the population doing HTTPS ruleset contributions will reach the level of "spam". In fact, the problem is the exact reverse. Often, people simply don't know what HTTPS is, or what it does (even now.) I myself have reached out to sites with sensitive content to ask them whether they'd consider adopting HTTPS, and they have personally thanked me for the tips and responded that yes, they would implement it.
This is a win, period. If someone is annoyed by a friendly email asking them to protect their users, then so be it. Hopefully they'll be annoyed beyond a certain threshold, to actually start protecting their users.
Perhaps one of the things we can do in any new ruleset intake system (as discussed in #3069, #6322) would be to have a field for when the last time a site owner has been reached out to. This way that owner won't accidentally get multiple emails asking them to move their site to HTTPS. I honestly don't see this as being a realistic problem, but it's not as if this is an intractable problem if people are actually worried about it
I actually don't know what this issue is for. No one needs the EFF's permission to send an email to a webmaster asking them to enable HTTPS. So what is specifically being proposed?
Drawing out this suggestion to add info about how to find site owners email addresses might be helpful, and if we do have an intake system that supports it, adding info which indicates a site owner has been contacted.
If this issue is just to encourage the EFF to share tips in the FAQ about convincing site owners to implement HTTPS, then I'm fine with that (FWIW). It may be worthwhile to add in the FAQ that
any contact to site owners should be personalized and absolutely not mass-emailed, to provide cover for the EFF in case an over-eager privacy advocate comes up with a (web crawler+email service+simple script) spammer, and
the person reading the emails may not have any decision-making authority and may in fact already be on-board with HTTPS and so the person sending the email should not, you know, be mean about it.
I'm sure you @Hainish and others at the EFF can judge well enough whether these problems are important enough or likely enough to mention.
Closing for now, we offer guidance on how a site owner can upgrade their site. There's no streamlined way to currently contact site owners. Been thinking of how we can do that, but so far, tools like Let's Encrypt do a good job for those who may have been routed thanks to Chrome and FireFox having proper indications in place that one's site is not secure. API calls are starting to fail, mixed content is being blocked now, etc.
Activity
jeremyn commentedon Apr 17, 2017
It would be nice to clarify the relationship we want with site owners. We've generally been very accommodating to site owners, however my experience with them has usually been that if there is any ambiguity or difficulty, they would prefer that we not include their site in the add-on. This makes sense if you think about it: HTTPS Everywhere can break the experience for users, break ads, and is outside of the site's direct control and requires a technical person's time to work with us to fix problems. They can use HSTS if they want what HTTPS Everywhere does.
Hainish commentedon Apr 17, 2017
We can specify this in the FAQ and perhaps this belongs in
CONTRIBUTING.mdas well.Something like:
Bisaloo commentedon May 4, 2017
What I really would like to see is a small email template we can use to write to website owners.
Many contributors (myself included) are not native speakers and therefore don't always convey ideas in the most clear and efficient way.
A template explaining why
httpsmatters and how eventually it is to going to be mandatory (given Google and Mozilla stance on this) would help a lot with this issue.jeremyn commentedon May 4, 2017
On further thought I'm not sure what this issue/proposed FAQ update is for. When I've contacted site owners, it's because I want their help to write a rule because there is something unusual or difficult about their site. An email template wouldn't help with that because each problem is unique.
We don't need to email site owners about why HTTPS is important. The tech people at these sites that we talk to know about HTTPS and why it's important, they want to support it, and they are competent enough to do it. However unless the site is trivially small or was built from the start to support HTTPS, actually deploying HTTPS is complicated by stuff like CDNs, ad networks, analytics, competing business needs, testing requirements etc. Emailing them a beginner's level description of HTTPS when they are already fighting the HTTPS battle with their management and customers will not help.
jeremyn commentedon May 4, 2017
Also, of course, we are only able to create rulesets for sites because those sites have already gone to the trouble of at least partially supporting HTTPS. We are always building on the work of the site owners.
Bisaloo commentedon May 4, 2017
I don't argue with that. But I don't think site owners are necessarily the same people as site developers. You also seem to talk only about "big" websites but those are not the targets I have in mind for this kind of email.
For example, some independent news websites don't support https. It may be because they don't realise that all their traffic is in clear text. The people who run it are not always tech literate. I believe in this case, a short email saying that as a user, you would like to protect your privacy and how https helps with that would be great. Even if they are already aware of the issue, proof that it matters to their users may motivate them to focus more on it.
Then, I agree their tech are surely capable enough to take care of the technical stuff or they can easily seek help. Hence the fact I didn't mention it in my proposed points for a template.
Hainish commentedon May 4, 2017
At EFF the canonical resource we've used to explain the importance of HTTPS is our "Encrypting the Web" page: https://www.eff.org/encrypt-the-web
This specifically has a "What you can do as a web site owner" section. I would not assume that any site we're interested in adding coverage for already knows the importance of HTTPS. Often, those offering very sensitive information just haven't thought about offering HTTPS, or don't really know what it provides.
I think an email template would be fine, but definitely linking site owners to the "Encrypting the Web" page is best practice.
jeremyn commentedon May 4, 2017
Professional site admins would not appreciate random emails with basic HTTPS information and would probably consider it spam from the EFF. Low-tech people who, perhaps, barely managed to follow a tutorial to buy a domain name and set up a WordPress blog on shared hosting, will not know what to do with this information and will have many questions. I'm having trouble picturing a webmaster@example.com in 2017 who is both low-tech enough to need basic information, but high-tech enough to figure the rest out on their own.
The EFF does good work in raising general awareness and changing the public mindset about encryption. This makes it easier for players like Google and Mozilla to make HTTPS the default and plain HTTP be seen as deficient. This is not the same thing as directly emailing specific site owners/admins.
My own take is that nobody should email a site owner/admin trying to convince them to use HTTPS unless that person is willing to patiently answer their questions. If they send the email out claiming any association with the EFF at all, even as a volunteer, then they should be willing to answer those questions for free.
jeremyn commentedon May 4, 2017
Also keep in mind that even tiny businesses and nonprofits will have technical people involved in making the websites, often as part-time help from a consulting agency.
Hainish commentedon May 4, 2017
I have a hard time trying to convince myself that the level of email traffic generated by the proportion of the population doing HTTPS ruleset contributions will reach the level of "spam". In fact, the problem is the exact reverse. Often, people simply don't know what HTTPS is, or what it does (even now.) I myself have reached out to sites with sensitive content to ask them whether they'd consider adopting HTTPS, and they have personally thanked me for the tips and responded that yes, they would implement it.
This is a win, period. If someone is annoyed by a friendly email asking them to protect their users, then so be it. Hopefully they'll be annoyed beyond a certain threshold, to actually start protecting their users.
Hainish commentedon May 4, 2017
Perhaps one of the things we can do in any new ruleset intake system (as discussed in #3069, #6322) would be to have a field for when the last time a site owner has been reached out to. This way that owner won't accidentally get multiple emails asking them to move their site to HTTPS. I honestly don't see this as being a realistic problem, but it's not as if this is an intractable problem if people are actually worried about it
jeremyn commentedon May 4, 2017
I actually don't know what this issue is for. No one needs the EFF's permission to send an email to a webmaster asking them to enable HTTPS. So what is specifically being proposed?
Hainish commentedon May 4, 2017
It looks like we already do have some copy about how one can reach out to site owners: https://www.eff.org/https-everywhere/faq#what-if-the-site-doesnt-support-https-or-only-supports-it-for-some-activities-like-entering-credit-card-information
Drawing out this suggestion to add info about how to find site owners email addresses might be helpful, and if we do have an intake system that supports it, adding info which indicates a site owner has been contacted.
[-]In FAQ, suggest reaching out to site owners[/-][+]In FAQ, add more info on reaching out to site owners[/+]Hainish commentedon May 4, 2017
I've changed the issue title accordingly
jeremyn commentedon May 5, 2017
If this issue is just to encourage the EFF to share tips in the FAQ about convincing site owners to implement HTTPS, then I'm fine with that (FWIW). It may be worthwhile to add in the FAQ that
I'm sure you @Hainish and others at the EFF can judge well enough whether these problems are important enough or likely enough to mention.
zoracon commentedon Jul 23, 2020
Closing for now, we offer guidance on how a site owner can upgrade their site. There's no streamlined way to currently contact site owners. Been thinking of how we can do that, but so far, tools like Let's Encrypt do a good job for those who may have been routed thanks to Chrome and FireFox having proper indications in place that one's site is not secure. API calls are starting to fail, mixed content is being blocked now, etc.