search

EFForg / https-everywhere

A browser extension that encrypts your communications with many websites that offer HTTPS but still allow unencrypted connections.
https://eff.org/https-everywhere
Other
3.36k stars 1.09k forks source link

Allow easier input of domains requested to be reviewed #6322

Closed Foorack closed 7 years ago

Foorack commented 8 years ago

Credits for this idea goes to @jeremyn

The idea was originally posted in https://github.com/EFForg/https-everywhere/issues/6307 Moving it here to keep the other issue clean from off-topic discussion.

The discussion left off with me saying:

users could tweet domains using some hashtag:

I like the idea as I am a Twitter user, however, not everyone have a Twitter account and I think it will be difficult to list and mark which are done.

What about using Google Forms and having it being saved in a Spreadsheet? Contributors could mark domains with its status and the spreadsheet would be public for read-access. Thoughts?

ghost commented 7 years ago

@jeremyn A week is enough for a user to fix the mistakes in an issue. If they do not fix the mistakes, then the issue is probably abandoned.

ghost commented 7 years ago

We need to allow specifying multiple domains in one issue as long as they have a common parent which is not a public suffix, else we are going to drown in issues.

jeremyn commented 7 years ago

@koops76 In my suggested instructions in https://github.com/EFForg/https-everywhere/pull/11615#issuecomment-330917544, my plan is that reporters put the highest common domain in the Domain: field and specific subdomains in the free-form description part. An issue might look like this:

Domain: example.com

Specifically one.example.com and two.example.com.

If a casual reporter notices that one.example.com should be covered, it generally means that the entire example.com ruleset needs to be created or updated.