Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
1–10 of 207 posts
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#2This makes sense, but I guess adblockers could just start loading the data and not show it to the user?
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#3TIL about HTTP 103, that's pretty neat.
It seems pretty easy to mitigate this by always loading the early hints though, as in Firefox should adopt Chrome's approach as described in the README.
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#4Sounds like it might make sense to drop this early hints feature (whatever it is).
I wonder how much longer it will be before the next major escalation happens with ad blockers. I can imagine mainstream browsers that fetch unmodified pages and click ads in the background (do subvert pay per click ad business models and make it harder to compute targeting metrics), but then display an ad/tracking-free version in a separate rendering pipeline.
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#5Sounds like it might make sense to drop this early hints feature (whatever it is). I wonder how much longer it will be before the next major escalation happens with ad blockers. I can imagine mainstream browsers that fetch unmodified pages and click ads in the background (do subvert pay per click ad business models and make it harder to compute targeting metrics), but then display an ad/tracking-free version in a sep…
As far as I know, current ad blockers can't block ads from Widevine (DRM protected) streams, so I guess it's only a matter of time until Chromium team comes up with Widevine for webpages and then it's game over for normal consumers.
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#6This makes sense, but I guess adblockers could just start loading the data and not show it to the user?
Can this also be solved by completely blocking early hints?
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#7Sounds like it might make sense to drop this early hints feature (whatever it is). I wonder how much longer it will be before the next major escalation happens with ad blockers. I can imagine mainstream browsers that fetch unmodified pages and click ads in the background (do subvert pay per click ad business models and make it harder to compute targeting metrics), but then display an ad/tracking-free version in a sep…
Even without early hints, i assume you could do the same thing with the link http header.
Or if you really dont care about performance, just loading the start (e.g. ) of the document and wait a little bit to see which subresources are loaded.
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#8Probably too unreliable to use in real life - for example, I suspect many crappy corporate proxies will block HTTP 103 responses as some unknown danger.
Re: Show HN: Detecting adblock, without JavaScript, by abusing HTTP 103 responses
#9Sounds like it might make sense to drop this early hints feature (whatever it is). I wonder how much longer it will be before the next major escalation happens with ad blockers. I can imagine mainstream browsers that fetch unmodified pages and click ads in the background (do subvert pay per click ad business models and make it harder to compute targeting metrics), but then display an ad/tracking-free version in a sep…
As far as I know, current ad blockers can't block ads from Widevine (DRM protected) streams, so I guess it's only a matter of time until Chromium team comes up with Widevine for webpages and then it's game over for normal consumers.
Don't be evil.