It's funny because the whole intercept thing is an escalation between ad networks and browser writers.
It's funny because the whole intercept thing is an escalation between ad networks and browser writers. ...and what I think is more unfortunate, those who do interception to filter out ads and other crap are caught in the crossfire. Browsers have extensions but to have to write and/or install one for each browser you use (which can be several, particularly if you're a web developer) and keep them in agreement with each other is a pain. It doesn't work for the browsers that are either embedded in apps or don't support any extensions (mobile...), and the abuse of extensions has lead to a situation in which browser vendors are trying to control what extensions you can use: Chrome: https://news.ycombinator.com/item?id=7237725 Firefox: https://news.ycombinator.com/item?id=9061592 What you can do in an extension with respect to blocking content is also limited by the fact that e.g. a div to be removed would have to be parsed and loaded by the browser before an extension could work on and remove it, whereas a filtering proxy could strip it out completely and spare the browser from having to read a single byte of it. In light of that, I see their "make an extension" statement as basically saying "instead of doing something more generic and cross-browser, we'll tell you to use something that we can have more control over, because security." No thanks.
Posted by userbinator on Feb 28, 2015, 4:04 AM
Tags
Related issues
- > Your blog post doesn't get found by anyone in Google until you've built up your SEO mojo, your LinkedIn post isn't read without the fol...
- I am obviously a very small player doing things as a hobby, I don't matter to Google.
- New DOM renderer for Flutter web
- Plugin Support for Custom Transformers
- It weighs thousands of pounds (of aluminum!), using a 600-pound custom frame and an even more massive support structure, using 6,400 thre...
- Passive income often connotes building something once, then sitting back while money pours in.
Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments
support (Marketing)
> Your blog post doesn't get found by anyone in Google until you've built up your SEO mojo, your LinkedIn post isn't read without the fol...
I am obviously a very small player doing things as a hobby, I don't matter to Google.
New DOM renderer for Flutter web
Plugin Support for Custom Transformers
It weighs thousands of pounds (of aluminum!), using a 600-pound custom frame and an even more massive support structure, using 6,400 thre...
Passive income often connotes building something once, then sitting back while money pours in.
It's funny because the whole intercept thing is an escalation between ad networks and browser writers.
It's funny because the whole intercept thing is an escalation between ad networks and browser writers.
It's funny because the whole intercept thing is an escalation between ad networks and browser writers. ...and what I think is more unfortunate, those who do interception to filter out ads and other crap are caught in the crossfire. Browsers have extensions but to have to write and/or install one for each browser you use (which can be several, particularly if you're a web developer) and keep them in agreement with each other is a pain. It doesn't work for the browsers that are either embedded in apps or don't support any extensions (mobile...), and the abuse of extensions has lead to a situation in which browser vendors are trying to control what extensions you can use: Chrome: https://news.ycombinator.com/item?id=7237725 Firefox: https://news.ycombinator.com/item?id=9061592 What you can do in an extension with respect to blocking content is also limited by the fact that e.g. a div to be removed would have to be parsed and loaded by the browser before an extension could work on and remove it, whereas a filtering proxy could strip it out completely and spare the browser from having to read a single byte of it. In light of that, I see their "make an extension" statement as basically saying "instead of doing something more generic and cross-browser, we'll tell you to use something that we can have more control over, because security." No thanks.
Comments (0)
No comments yet. Start the discussion.