[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4969 [EFF-HTTPS Everywhere]: Add new section in GUI for Newly Reported Websites, for faster merging
#4969: Add new section in GUI for Newly Reported Websites, for faster merging
----------------------------------+-----------------------------------------
Reporter: vic | Owner: pde
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: EFF-HTTPS Everywhere | Version:
Keywords: | Parent:
Points: | Actualpoints:
----------------------------------+-----------------------------------------
Changes (by zyan):
* priority: minor => normal
Comment:
It is true that there is a massive backlog of rulesets (~3000) that need
to get reviewed and merged from master to stable, and that we need a
better way of knowing when the master rulesets are "stable" than simply
the length of time that they've been in master.
I can see two ways to implement Vic's suggestion, as I understand it:
1. Allow people to download/add and modify rules at run time. (Is this
possible without re-compiling the extension?) We could present a UI
element in the toolbar menu that says "There is a rule for this site in
master; would you like to download and test it?"
2. Include all the master rules in stable releases but mark them as
default_off with a note that they need to be tested.
Either way, once #7075 has landed in stable, we will get bug reports on
rule disables, so we have some idea of when an unstable rule is
problematic.
Solution 1 has the benefit of making things like #2161 (subscription to
external rule feeds) easier.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4969#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs