Show explanation of why a domain is blocked

[kevwil]

I wanted to visit http://youmightnotneedjs.com/ but lots of content is missing. It seems PrivacyBadger is blocking everything from codepen.io. I'd like to know why, and make an informed decision of whether to change that domain's slider and allow content, but PrivacyBadger has no means of explaining why a domain is blocked. This seems like a missing feature.

[alexristich]

Good suggestion. The current algorithm doesn't track the specific details, but it's something we could potentially do. One of the main issues with this, however, is where it would be displayed in the popup. The UI could use some work (and there is chatter about how to best improve it), and trying to jam something else in before refreshing the design might just cause something to explode. ;)

I'm not sure where exactly this would fit in via scheduling, as I suspect it entails a good amount of work on the back end as well. If you're willing to take a stab at it or if someone else wants to have a go that'd be awesome!

[ghostwords]

Previously: #694, EFForg/privacybadgerfirefox-legacy#490 (comment).

[pde]

Interestingly, this somewhat conflicts with most of the solutions we've proposed for #266. Maybe there's a way to keep these records until history-clearing events, at which point we switch to the hash fragment form?

[cowlicks]

Something to keep in mind while designing that once we have better tracker level details we might want to extend this to cookie level details. A system like this would have helped with the cloudflare cookie issue #1237

Also there seem to be many issues about this. I can try to aggregate them this weekend, and hash out an implementation. I have not had much free hacking time lately due to work.

[ghostwords]

I don't see a way to be notified of history-clearing events at this time without asking for the "history" permission, which will trigger a new permission warning, which seems unacceptable for Privacy Badger at this point (will lose a significant percentage of users in Chrome, and have a similar percentage stop upgrading in Firefox).