List view
Version 1.x will address many requested features that are less critical than the features of version 1.0. Essentially, milestone 1.x is where tickets get assigned when they should be reevaluated for priority after 1.0 is released.
No due dateVersion 1.0 is a major rewrite of !RequestPolicy to support the following features: * Blacklists: rules that indicate request should always be blocked even if other rules would have allowed the requests. * Better rule system, including wildcard subdomains. * Subscription whitelists/blacklists. * Whitelist/blacklist stored in better format outside of user prefs file. Some tickets marked for this milestone are duplicates or will become invalid due to the major changes of 1.0. For some of these, targeting for 1.0 really means that I expect to be able to close the ticket one way or another once 1.0 is completed. This may be because the issue has become invalid or because the feature is approximated closely enough by other features in 1.0.
No due date•0/1 issues closed- No due date
Version 0.6 will likely add opt-in, privacy-aware telemetry to allow measuring user experiences such as amounts and types of UI (menu) interactions. This will provide a basis for understanding how the changes of version 1.0 are affecting users and impacting RP's usability.
No due date