browser-laptop
browser-laptop copied to clipboard
Preference to block third-party images
As mentioned in this comment, and requested elsewhere, users have requested third-party image blocking.
I don't think that blocking 3rd-party images specifically — as opposed to 3rd-party content in general, or cookies on 3rd-party content, or… — is a privacy issue.
@flamsmark what about content fetched which includes a tracking ID?
ex: http://example/tracking.jpg?id=123456
Multiple fetches using that tracking ID could establish a browsing pattern (on the 3rd party site)
It's definitely not a major concern, but could carry query parameters and/or your ip address off to unrelated parties. I'm not personally worried about this, but can see how others might be.
@bsclifton Is the tracking implication different when it's https://example/tracking.jpg?id=123456
as opposed to http://example/tracking.txt?id=123456
. That is: what's the relationship between the privacy consequences and the filetype being requested?
My preference is to combine this with other content-blocking requests into one integrated feature. I'm not sure what relationship that will have with the other Shields UI. Does that sound sensible, or is there good reason to work on this separately?
@flamsmark good call! Having a catch-all (regardless of file type) sounds great 😄