Skip to content

1.8.0

Choose a tag to compare

View all tags
@codepurse codepurse released this 24 Sep 13:28
· 57 commits to main since this release
1.8.0
2165f88

BlockNSFW 1.8.0: blocking moves into the browser

Until now, the extension stopped a blocked site only after the page had started loading. With 1.8.0, the browser itself refuses the request. This closes two gaps that have been there since the beginning.

🛡️ Blocked sites no longer receive the request

Before, you never saw a blocked site, but the site still saw you. Your address and cookies had already gone out by the time the extension stepped in. The full blocklist of 204,000+ sites is now enforced by the browser's own request engine, so blocked images, videos, frames and scripts are refused before anything is sent.

Visiting a blocked site directly still shows the BlockNSFW blocked page instead of a blank browser error, so you always know why something was blocked.

🧩 Content inside embedded frames is filtered

Filtering used to run only on the main page. Content inside an embedded frame was checked by address and nothing else, which made "iframe proxy" sites an easy way around the extension. Image, media and AI filtering now run inside frames too. Tiny ad and analytics frames are skipped, so ordinary pages stay fast.

🔒 The blocked page no longer leaves the address in your history

The blocked site's address, and the words that triggered the block, used to end up in your browser history and address-bar suggestions. With history sync on, they also reached your Google account. That information is now held in memory only and never written down.

If you have history sync on, entries from before this update may already be in your account. Clearing them is worth doing.

⚡ Also fixed

  • The AI image filter remembers its results again. Its cache had been failing silently on Chrome, so every image was re-analysed on every page. Pages with lots of images should feel noticeably lighter.

📦 Also includes everything from 1.7.7

1.7.7 was never published on its own, so its fixes arrive here:

  • Blogspot blogs and Mexican government sites are no longer blocked by mistake. If you whitelisted one to work around this, you can remove the entry.
  • A blocked-word pattern can no longer freeze a page.
  • Sites can't slip past the keyword filter by having an ordinary word like "safe" or "help" in their address.
  • A website can no longer inject its own content into a custom HTML blocked page.
  • Nothing about your browsing is written into the page's console any more.
  • Blocked videos and embedded content are counted in your stats again.

⬆️ Upgrading

Nothing to do. Your settings carry over.

  • Chrome 101+ is now required. Network-level blocking needs it. Chrome updates itself, so this affects almost nobody. Older browsers stay on 1.7.7. Firefox is unchanged (113+).
  • If a site you allowed still looks partly blocked, reload it once.
  • Blocked-word patterns that nest repeats, like /(a+)+/, no longer match. Rewrite them without the inner +.
  • A site may be newly blocked if its address contains one of the eight over-broad "safe" words removed in 1.7.7. Whitelist it, and please report it.

Install

Full technical details are in CHANGELOG.md.

Assets 2
Loading