Hacker News Reader

Apple screwed the pooch too, they were the first one to prevent blocking content before downloading it if I recall. Then Chrome did the same thing. I'm not sure what their reasoning was publicly, but it was surely lying.

A browser should allow you to not download content by URL masks, and not silently load it and hide it. This is advertising/tracker shenanigans and frankly horrid tech.

View on HN

There is some fundamental misunderstanding here because content blockers can block requests by url.

Interesting. Tell me what's the difference with content blockers before and now? Maybe I am. But the content blockers in the past had more control on what to block.

I think what you are discussing is the move to only supporting declarative block lists. Long ago in Safari, and until very recently in Chrome, you could have JavaScript run to check and modify/block requests. The modern block lists still function the same (preventing a Request from ever being sent) just without dynamic code in the loop.

Reply on news.ycombinator.com