Alexei

Alternatively, we could make it so that disabling PB on a Google property also disables PB on `www.google.com`. This is much simpler, but we should consider the downsides.

Oh, also, the Google tracking redirect doesn't always go through `www.google.com` but could be one of the Google country code domains?

Hello everyone! Like I wrote in my Chrome Web Store review reply, this is a bug in Chrome that may get fixed by Chrome version 128. Until then, I should...

OK, it's just that `link.bilibili.com` doesn't seem to be blocked by EasyList/EasyPrivacy, DDG or Ghostery, and I would add an exception to allow it to load w/o access to cookies,...

This should be fixed in Chrome as of Chrome version 128. @Mishasama Could you take a look, and perhaps update your Chrome Web Store review? Thank you!

Hello and thanks for opening an issue! It looks like PB is pretty fundamentally broken, and the google.com/url thing (Google link tracking redirect removal) is a symptom of a bigger...

Could you navigate to `chrome://extensions`, enable "Developer mode" in the upper right corner (if it isn't already enabled), and click the "service worker" link inside Privacy Badger's listing on this...

Also, have you had PB installed and working already for some time and this started recently, or did you recently install PB and immediately ran into this issue?

I think it's no-cache because (a) the icon is a local extension resource, and (b) that's just [how Chrome implemented this](https://groups.google.com/a/chromium.org/g/chromium-extensions/c/3Z90cTGePPY/m/afEN4TTDAQAJ). Your PB service worker console log looks fine to...

Thanks for the info! The Global Privacy Control errors are unrelated. The "source image could not be decoded" errors suggest this is the same problem as what I attempted to...