Jev Ad Blocker

05 / WHY CODE FINDS CANDIDATES FIRST

Narrow the search space before semantic judgment

This demo uses fixed simulated fixtures so extraction remains verifiable. It does not claim to be a general-purpose DOM detector, and it never sends raw HTML, scripts, cookies, or a whole page source to Jev.

02 / USE ON REAL WEBSITES

Run the community browser extension

The live demo above runs on a fixed simulated page through this site's server API. For real websites, realZachi/typesafe-adblock ↗ is a separate, bring-your-own-key Chrome extension. Review its source and permissions before installing it.

1. Get the verified source.

   Clone the repository and check out the version reviewed here. The repository root contains manifest.json and the referenced src/ files; this version needs no npm install or build step.

   Terminal · source checkoutGit

   git clone https://github.com/realZachi/typesafe-adblock.git
   cd typesafe-adblock
   git checkout 7e067d243d87b7fe4d511653c0ddcd77b9beee18

2. Load it locally.

   In Chrome, open chrome://extensions, turn on Developer mode, choose Load unpacked, and select the cloned typesafe-adblock folder containing manifest.json. This is a source install; we have not verified a Chrome Web Store listing for this project.

3. Configure your own key.

   Open the extension popup, enter your own TypeSafe API key there, and select Test to check access. Then browse an HTTP(S) website and use the popup's threshold and Remove or Highlight only mode. Model calls use your key and may incur charges. Do not paste a key into this website or the repository source.

Source checked at realZachi/typesafe-adblock@7e067d243d87b7fe4d511653c0ddcd77b9beee18. Installing the extension is optional; it is not required for the demo above.

03 / TWO DISTINCT DATA FLOWS

What runs locally, and what leaves the browser?

07 / TWO COMMUNITY APPROACHES

A live ad judgment and reusable cleanup rules solve different jobs

Source checked at kitze/unclutter@9ef9beccc1e57b4e3115ae68644b8fc9c19c29f6. Its saved rules and provider settings do not apply to this site's demo or to typesafe-adblock.

08 / IMPLEMENTATION

Evaluate candidates once, then change ordinary UI state

The short example preserves the boundary: Jev returns probabilities; hideElement(...) belongs to application code. The Jev API guide covers the validated server endpoint and provider setup.

const candidates = findCandidates(pageFixture);

const questions = Object.fromEntries(
  candidates.map((candidate, index) => [
    candidate.id,
    boolean(`Is candidate C${index + 1} a paid advertisement?`),
  ]),
);

const result = await evaluate({
  state: describeCandidates(candidates),
  questions,
});

const hidden = candidates.filter(
  (candidate) =>
    result.answers[candidate.id].probability >= threshold,
);

// Application code owns the reversible visual change.
hidden.forEach((candidate) => hideElement(candidate.id));

04 / HOW IT WORKS

Five bounded judgments, one reversible page change

09 / LIMITATIONS

Visual hiding is not network blocking

This demo and the community extension hide page elements after semantic classification; they do not block the underlying network request. Neither replaces request blocking, tracker or malware protection, cookie blocking, video-ad blocking, or a rules engine such as uBlock Origin.

10 / SOURCES & NEXT STEPS

Study the pattern, then build a bounded decision

• realZachi/typesafe-adblock source ↗
• kitze/unclutter source ↗
• TypeSafe Noul probability ↗
• TypeSafe parallel questions ↗