Browse code

Dropping 'Automated Reporting of Buggy Rulesets'

Yan reports that this was part of her OPW project last year. It's mostly done.

Damian Johnson authored on04/02/2014 17:42:27
Showing1 changed files
... ...
@@ -1069,39 +1069,6 @@ meetings around the world.</li>
1069 1069
     </p>
1070 1070
     </li>
1071 1071
 
1072
-    <a id="reportingBuggyRulesets"></a>
1073
-    <li>
1074
-    <b>Automated Reporting of Buggy Rulesets</b>
1075
-    <br>
1076
-    Effort Level: <i>Medium</i>
1077
-    <br>
1078
-    Skill Level: <i>Medium</i>
1079
-    <br>
1080
-    Likely Mentors: <i>Peter Eckersley (pde), Micah Lee</i>
1081
-    <p>
1082
-When users manually disable an HTTPS Everywhere ruleset via the toolbar menu,
1083
-that's a strong hint that that ruleset might be buggy.  If we could obtain
1084
-statistics about which rulesets are manually disabled by the users of which
1085
-HTTPS E versions, we could get a statistical picture of which rulesets need
1086
-the most urgent debugging and/or disablement.  This would enormously improve
1087
-the quality of the HTTPS Everywhere user experience.
1088
-    </p>
1089
-
1090
-    <p>
1091
-HTTPS Everywhere already includes a pipeline for anonymised user submissions
1092
-(via Tor where available) that is used for the Decentralized SSL Observatory.
1093
-We should do a popup that asks the users to submit anonymous reports of
1094
-disabled rules, when they manually disable one for the first time.
1095
-    </p>
1096
-
1097
-    <p>
1098
-Perhaps this feature could optionally let users submit the URL of the page
1099
-they were looking at when the bug occurred, although we would need to take
1100
-care in handling those, and perhaps implement some countermeasures against
1101
-sending passwords or auth tokens when URLs contain those.
1102
-    </p>
1103
-    </li>
1104
-
1105 1072
     <a id="httpsEverywhereRulesetTesting"></a>
1106 1073
     <li>
1107 1074
     <b>Incorporate Ruleset Testing into the HTTPS Everywhere release process</b>