Home › Scope

I explain the scope

I put this site together as a narrow set of notes: why a gambling blocker is not recovery, which device paths still open online casinos and sportsbooks, how a reader might assemble a local WebExtensions block, and which gaps I expect afterward. It is written for technically curious adults who want fewer accidental openings, not for anyone looking for odds, bonuses, or operator reviews.

The voice is first person because the decisions are sequential and easy to blur. I still do not describe a personal gambling history, a clinic I visited, or a filter I measured on someone else’s network. Where I am unsure — about a browser key, a menu label, or a legal age that changes by state — I say so and point to the organisation that maintains the fact. Named sources include the National Council on Problem Gambling, SAMHSA, MedlinePlus, Mozilla Firefox, Chromium, WebExtensions, and OWASP, each for the stable role it has long held.

The pages are evergreen general information written for this site. They are not a news service, not a live status board, and not personal, legal, financial, or medical advice. Platform screens move. If a control’s name has changed, the vendor’s own help is the check, not a sentence here.

What I will not do is block traffic for you, host an installable add-on, list gambling businesses, explain how to reach a site that a filter closed, or suggest that any configuration produces a better outcome at play. Gambling can cause harm. Help is a human and public-health matter; a stylesheet cannot supply it.

On accessibility, I rely on a skip link, visible focus, readable contrast between light grey text and charcoal surfaces, labels on the draft fields, and a reduced-motion preference that turns off smooth scrolling. I do not claim a certified conformance level. If a control fails for you, use the draft page to prepare a note. Nothing on that page is transmitted by the site.