Yesterday (19/08/2023) everything worked fine. Today (20/08/2023) I can no longer login to Twitch using Firefox. I restarted browser and cleared cache. No change.

EDIT: I tried again after 30min and it works again. I have some privacy-oriented plugins but I don’t play with custom useragent.

    • @[email protected]English
      6•11 months ago

      Ublock origin blacklisted trackers list might not be exhaustive so privacy badger will pick up.

      Btw I’d love to have a nice explanation on how it works if you think I’m wrong

      • 👁️👄👁️English
        7•11 months ago

        Posted this in another comment, but this is why:

        Thanks to disclosures from Google Security Team, we are changing the way Privacy Badger works by default in order to protect you better. Privacy Badger used to learn about trackers as you browsed the Web. Now, we are turning “local learning” off by default, as it may make you more identifiable to websites or other actors.

        From now on, Privacy Badger will rely solely on its “Badger Sett” pre-trained list of tracking domains to perform blocking by default. Furthermore, Privacy Badger’s tracker database will be refreshed periodically with the latest pre-trained definitions. This means, moving forward, all Privacy Badgers will default to relying on the same learned list of trackers for blocking.

        https://www.eff.org/deeplinks/2020/10/privacy-badger-changing-protect-you-better

        It’s just using filters like uBlock Origin since the training was considered a critical security issue that fundamentally broken. The article is the devs talking about it in more indepth.

        • @[email protected]English
          0•11 months ago

          I still use both, and already knew about this change. Is it useless overkill to keep both? Probably. But Privacy Badger also enables the GPC signal to let sites know you want to opt out of data sharing under the CCPA and GDPR. (You can enable GPC in about:config in Firefox, but that’s a hassle to do on every device, and extensions can be synced across devices)

          I’m sure there’s plenty of discussion to be had around the effectiveness of the GPC, but to be it’s worth it even if it’s just as a stat of users that care about data privacy. There’s also always a chance that something makes it to Privacy Badger’s Blocklist before uBlock Origin’s (although it’s probably more likely to be the other way around).

          • 👁️👄👁️English
            8•11 months ago

            Thanks to disclosures from Google Security Team, we are changing the way Privacy Badger works by default in order to protect you better. Privacy Badger used to learn about trackers as you browsed the Web. Now, we are turning “local learning” off by default, as it may make you more identifiable to websites or other actors.

            From now on, Privacy Badger will rely solely on its “Badger Sett” pre-trained list of tracking domains to perform blocking by default. Furthermore, Privacy Badger’s tracker database will be refreshed periodically with the latest pre-trained definitions. This means, moving forward, all Privacy Badgers will default to relying on the same learned list of trackers for blocking.

            https://www.eff.org/deeplinks/2020/10/privacy-badger-changing-protect-you-better

            • @[email protected]English
              2•11 months ago

              I was unaware of that change, even their website still promote heuristics.

              That being said, it’s not the same list as uBlock origin so you might have trackers going through ublock origin blocked by privacy badger or the opposite.

              My point is, why not use both ?

              • 👁️👄👁️English
                2•11 months ago

                uBlock filters already covers everything privacy badger blocks. It’s better to have less extensions then more. More code that can cause security issues, which is why local learning was disabled in the first place. More is not always better.

          • Kilgore TroutEnglish
            3•11 months ago

            That used to be the default behaviour, now it’s disabled but you can still enable this feature in its settings.