4 ms·
why don't we block ads at the operating system level instead at the browser level? If we are talking about having more security and performance wouldn't it more
by lfmunoz4 3y ago
why don't we block ads at the operating system level instead at the browser level? If we are talking about having more security and performance wouldn't it more sense? Not sure I understand how ublock origin works anyone have a summary on this?
- downWidOutaFite 3y agoMost of the network streams are encrypted at the os level.
- hjek 3y ago> why don't we block ads at the operating system level instead at the browser level? sure, we do that, too: https://github.com/StevenBlack/hosts https://github.com/StevenBlack/hosts
- vitorgrs 3y agoWhy operating system level and not network level? See Pi-Hole (or NextDNS, Adguard DNS)
- orthecreedence 3y agoBut this would make Windows 10+ unable to boot =[
- pythux 3y agoThe operating system level does not have as much information as the browser so it would be much less effective. You could do domain-level blocking (mostly) but miss lots of granularity on URLs, types of requests, contexts of request (what's the URL of the parent frame?), etc. Also it would be impossible to perform cosmetics injections (scriptlets, alterations of the DOM, etc.) It might already provide a good base-line but definitely not enough for all cases (e.g. YouTube ads, etc.)
- abwizz 3y agobecause the operating system can't see what's going on inside the connection or even know about the semantics of individual elements, the user-agent does that. the value of dns/ip level blocking is diminishing as resource density per host increases due to ipv4 shortage and should be completely inpractical with ipv6 due to adress space size.