{"action":"opened","issue":{"url":"https://api.github.com/repos/EFForg/privacybadger/issues/1645","repository_url":"https://api.github.com/repos/EFForg/privacybadger","labels_url":"https://api.github.com/repos/EFForg/privacybadger/issues/1645/labels{/name}","comments_url":"https://api.github.com/repos/EFForg/privacybadger/issues/1645/comments","events_url":"https://api.github.com/repos/EFForg/privacybadger/issues/1645/events","html_url":"https://github.com/EFForg/privacybadger/issues/1645","id":256011659,"number":1645,"title":"Consider out-of-band domain migrations to fix heuristic errors","user":{"login":"cowlicks","id":598099,"avatar_url":"https://avatars0.githubusercontent.com/u/598099?v=4","gravatar_id":"","url":"https://api.github.com/users/cowlicks","html_url":"https://github.com/cowlicks","followers_url":"https://api.github.com/users/cowlicks/followers","following_url":"https://api.github.com/users/cowlicks/following{/other_user}","gists_url":"https://api.github.com/users/cowlicks/gists{/gist_id}","starred_url":"https://api.github.com/users/cowlicks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cowlicks/subscriptions","organizations_url":"https://api.github.com/users/cowlicks/orgs","repos_url":"https://api.github.com/users/cowlicks/repos","events_url":"https://api.github.com/users/cowlicks/events{/privacy}","received_events_url":"https://api.github.com/users/cowlicks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-09-07T17:22:12Z","updated_at":"2017-09-07T17:22:12Z","closed_at":null,"author_association":"MEMBER","body":"It would be nice to be able to \"unblock\" domains that were erroneously blocked by privacy badger. I'm imagining something like a migration, except it can be delivered outside of privacy badger updates, like the yellowlist, or DNT hashes.\r\n\r\nWe have 2 kinds of migrations:\r\n* a kind where we change the schema of our storage\r\n* a kind where we unblock mistakenly blocked domains\r\n\r\nThis would address the second kind. We'd be able to more quickly deliver fixes to users, to give them a better experience. Some times where this would be useful:\r\n* When we've broken stuff by having a bad heuristic or some other bug.\r\n     - Like when we broke a bunch of sites because we remove some entries from the yellow list. We could have sent fixes without doing a release.\r\n     - unblocking domains which were blocked by __cfduid cookies\r\n* when we are unable to reproduce the tracking that cause something to be blocked. So we need to unblock it. See the [unable to reproduce issue label](https://github.com/EFForg/privacybadger/issues?q=is%3Aopen+is%3Aissue+label%3A%22unable+to+reproduce%22).\r\n     - youtube is a good example of this right now. We would be able to try try unblocking domains related to youtube. This might help, and improve the user's experience even though we don't know what is happening.\r\n     - #1153 we've spent a lot of energy investigating it. A good stopgap measure would be unblocking it with a simple migration. Instead of spending more time searching for the cause of the tracking.\r\n\r\nThis would also be nice because our migration system is pretty clunky. Removing domain unblocking from it would make working with it much simpler, and therefor less error prone."}}
{"actor":{"display_login":"cowlicks"}}