OC Ad Bye-Pass Chrome extension security report

Getting to the thing you came for takes a few dismissals. Close the cookie wall, close the newsletter box, close the open-in-app banner, close the window you never clicked. By then the ads have settled in. This stops them arriving. The work went into one question: what should come off the screen, and what should not. · Ad and tracker requests, stopped at the address. Nothing is fetched, so nothing is drawn and nothing is spent in data. · Leftover ad slots, hidden. Korean site rules ship alongside the global ones, so domestic portals, forums and news sites are covered too. · Cookie consent walls, and the newsletter and app-install nags that come with them. · Windows that open out of nothing you pressed. Links and buttons you actually clicked still open. · On video sites, ads are cut out of the response before playback. There is nothing left for you to skip. Click the icon, choose "Pick element", and tap the thing on the page to take out that one thing. No F12, no DevTools, and no need to know what a selector is. Arrow keys widen or narrow what you picked. An extension that runs everywhere can break anything. So it switches off per site. Click the icon and drop that site's switch, and subdomains stop with it. When the only recourse for a broken page is uninstalling, people uninstall. Blocking rules update separately from the extension, so a site changing its markup does not mean reinstalling. Your per-site exceptions and the rules you wrote yourself save to a file, and load back from it. Your data stays yours. There is no account and no server. Everything happens inside your browser, and what you looked at goes nowhere. The only thing fetched is the rule list, and that is data — selectors — not code that runs. Open source, GPLv3: github.com/jshsakura/oc-ad-bye-pass