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.
General rule of thumb: If you suddenly encounter issues with your webbrowser, always check with another, clean profile. Preferably without any extensions.
Just chiming in as a software engineer. My product DOES support Firefox, but there are some weird animation quirks that my team has been trying to solve, but with limited bandwidth and a full product backlog, it’s hard to justify spending too much time supporting a browser with such small global utilization. Especially since we’re using third party libraries like angular material, quirks on smaller browsers can be a nightmare to chase down
Oh I fully understand a smaller company having a website that says “some animations may not work with your browser” when it’s obviously easier to just do chromium as that covers almost every browser, but fully disabling the entire website when it works just fine as long as you tell Firefox to say it’s chrome is a different story.
If you dont mind whitelisting cookies for the twitch domain, you can allow finger printing, log in, choose to stay logged in for 30 days, then disable finger printing again. And then you’ll only have to worry about it once a month.
uBlock blocks things solely based on them being in a filter list. Privacy badger blocks form controls and html elements that can allow tracking. Those are different things.
Does uBO replace/block fb widgets on sites? It was the main reason I kept Privacy Badger alongside it and just didn’t bother removing when uBO just got more advanced.
EDIT: to the dumbfucks downvoting this comment I’ll clarify so you can learn something today :
uBlock Origin and Privacy Badger are not the same thing. Privacy badger is focused on blocking trackers but wont block ads.
uBlock origin will try to block trackers based on a list, but it might not be updated or exhaustivew That’s where privacy badger comes handy, it should pick up most of trackers that will go through uBlock origin.
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.
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.
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.
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.
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.
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).
Twitch's official stance is to support the latest two versions of Firefox. Are you modifying your browser agent string at all? Or using any plugins that are privacy/ad-blocking related?
Add comment