Alexei

It was an idea meant to reduce the amount of stuff that needs to change. I didn't consider that the scripts need to work differently though: messaging to get go-ahead...

Hello and thanks for getting in touch! I see these "Something went wrong" messages all the time myself, with or without using Privacy Badger. Reloading the Twitter page once or...

This looks like the same bug as https://github.com/EFForg/privacybadger/issues/2706#issuecomment-729118487. Because `https://s2.washingtonpost.com/2e46378/` is a 302 redirect and because Twitter uses Service Workers, Privacy Badger gets confused (when the Service Worker for Twitter...

Until we figure out a way to deal with the underlying issue in Privacy Badger, you should be able to work around this error on Twitter by reloading the page...

I think this is another Google Analytics-related problem: You first get first-party GA cookies and then you see them in third-party contexts (#367).

No other user error reports at this time.

Resolving as we haven't had other reports, and this shouldn't be a problem going forward now that Privacy Badger catches Google Analytics by default.

Ah, I see, there is another cookie, "X-Mapping-fjhppofk". It gets set for me by https://members.orcid.org/sites/default/files/vector_iD_icon.svg on https://r-spatial.github.io/sf/

Hi @llrs, I am not sure what you mean by "redirect towards ORCID website". Could you describe how to reproduce your issue?

Hello and thanks for getting in touch! When you say that adding the site to disabled sites doesn't help, are you doing this via the "Disable Privacy Badger for this...