Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

µBlock dynamic filtering: default deny

github.com

Post reply on HN
Print view View original

81–87 of 87 posts

Re: µBlock dynamic filtering: default deny

#81

Post by lloeki »

cantlin wrote: post #53

As the author was kind enough to pick us as an example, here's some background on what some of those requests are doing. hits.theguardian.com points to our Omniture implementation, which is the main tracking suite used for macro-level reporting (like when we say we have X unique monthly browsers, or whatever). So if you want to be invisible to that, leave it blocked. ophan.theguardian.com points to our own analytics…

> It would be cute if there was some way of us hinting to the plugin which domains were needed to not break the site, though likely impractical in the real world.

Sounds like RFC 3514, only negated.

Re: µBlock dynamic filtering: default deny

#82

Post by Ntrails »

Redoubts wrote: post #37
username223 wrote: post #14

Denying 3rd-party resources by default is nice, but definitely experts-only. Pages will break in weird ways when half their rat's nests of JavaScript are missing, and it will take some coding knowledge to figure out which parts are necessary. I may switch to this myself, but I think I'll keep telling friends and family to use Ghostery

Reminds me a lot of the first time using NoScript. Figuring out which domains added functionality, and which just unleashed another tree of third party domains that may or may not unlock the content. Fun, for certain definitions of the word.

I came up with a simple rule for that. If I've got to temp unblock more than 3 things in NoScript to get to the content, it's not worth the effort.

Re: µBlock dynamic filtering: default deny

#83

Post by 7952 »

stingraycharles wrote: post #73
quadrangle wrote: post #71

Earlier quoted context omitted.

Yeah… I was told by someone that if everyone started blocking 3rd-party domains, the advertisers would start figuring out how to deliver their content through the server-side of the 1st-party so that it would be even less clear this was happening. In other words, there's already a way to hint at the plugin that something is needed: deliver it from the primary domain. This is obviously a complex battle for the long ha…

As someone who has built and exited an adserving SaaS in the past, I get asked this question almost never -- the advertisers that spend the most money never want to abuse the law. The same goes for the SuperCookie; everyone knows the technology exists, but it's only the rotten apples in the industry ruining it for everyone else by actually making use of it. I got asked whether we would support this a few times, but i…

We do seem to have to worse of all worlds at the moment. It is very difficult for users to exercise control over good sites, and it is practiaclly impossible to control bad sites.

I wonder if a solution would be to tie third party cookies to the parent page. So that by default a Facebook cookie on a Guardian page could only be retrieved when the user is on the Guardian website. You could then have options within ther browser to explicitly allow cross domain cookies if the user wants (and send the actual Facebook domain cookie).

Re: µBlock dynamic filtering: default deny

#84

Post by stingraycharles »

7952 wrote: post #83
stingraycharles wrote: post #73

Earlier quoted context omitted.

As someone who has built and exited an adserving SaaS in the past, I get asked this question almost never -- the advertisers that spend the most money never want to abuse the law. The same goes for the SuperCookie; everyone knows the technology exists, but it's only the rotten apples in the industry ruining it for everyone else by actually making use of it. I got asked whether we would support this a few times, but i…

We do seem to have to worse of all worlds at the moment. It is very difficult for users to exercise control over good sites, and it is practiaclly impossible to control bad sites. I wonder if a solution would be to tie third party cookies to the parent page. So that by default a Facebook cookie on a Guardian page could only be retrieved when the user is on the Guardian website. You could then have options within ther…

There is no reason limiting adservers from doing what you describe using first party cookies: they all make use of Javascript, so it is trivial to just set a first-party cookie.

We actually took that approach to be compliant with the EU's cookie law; if a visitor rejected third party cookies, we fell back to first party cookies.

Re: µBlock dynamic filtering: default deny

#85

Post by Max_Mustermann »

imthatgirl_08 wrote: post #64

Please someome help me! I figured out that through my internet/WiFi my boyfriends laptop has full rights over my phone, cable and the WiFi. All my app versions are version 1 basically and tons of 3rd party restrictions. My bing,Google,Facebook,yahoo,comcast, Microsoft,Outlook and whatever you can name redirects all websites and emails I've figured out everything but not 100 prevent how to get it off completely. I kno…

This kind of questions are not really expected or wished for on Hacker News, AFAIK. I would try the subreddit /r/techsupport : http://www.reddit.com/r/techsupport

Re: µBlock dynamic filtering: default deny

#87

Post by bsilvereagle »

bhouston wrote: post #19
bsilvereagle wrote: post #17

Earlier quoted context omitted.

Piwki would be fine if it was hosted on a subdomain of the first party domain. If you visit test.com, piwki.test.com would work. However, piwik.not-test.com would be blocked.

Last time I check piwik is always blocked no matter the host.

Yeah, you're right. In the latest release, piwik is blocked. I hadn't tried it recently.
Post reply on HN