Is there a reason you can't use the declarative API to block these websites? Isn't that what you're doing on Safari?

https://developer.chrome.com/docs/extensions/reference/decla...

(Disclosure: I work at Google, speaking only for myself)

So, if I read this correctly, there's no way to modify the results of a request anymore? I can just redirect to a new URL, block or allow? I' m not even sure, upon reading that, if I can use JS to redirect based on the full URL not just the matching snippet to a new URL.

I wrote that previous comment before I fully understood the new specification. I'm still not entirely sure, but it looks like you're right.

I thought the rules were static, I see now they can be updated dynamically — which works perfectly for my use case.

Develop it for Firefox and recommend people to remove Chrome as part of using it? Though it has Leechblock already.

I have a firefox version, and a safari one in the works. It has about 50 users on firefox and 1500 on chrome.

It works a bit differently to most content blockers, you can take a look here if you're interested:

https://prodtodolist.com

Anyway, the whole point is to allow people to get out of addictive loops, to take control of how they use the web, and most people aren't that tech savvy — they deserve to not be addicted to facebook too.