Yesterday i upgraded ff to the current version and since today i experienced problems with a bunch of different sites. Either the cloudflare verification sends me into a loop or i get through and the site’s not working correctly. Some others work, though.
Disabling add-ons (noscript, ublock) and allowing all cookies didn’t help. Most work with microsoft edge, but i don’t know if the others worked with edge before.
Does somenone have info on that or experienced the same problem? I’m not sure is it just a coincidence or does the update cause the problems.
Edit:
I found a workaround for some. First i set the cookie block from “all cookies” to “all cross-site cookies”, then i allowed via STRG+i to set cookies for the refreshed page. Then i set the cookie block back again.
I assume cloudflare changed the address for some of their cookies which got blocked by ff.
The only one still not working (so far) is suprfit.com. It’s not a big shop, their software might produce their own shenanigans. I’ll shoot them a mail later.
Edit2:
suprfit.com works now too. Whatever it was got fixed.
I’ve read not to bother with Decentraleyes. The dependencies are often out of date which mean you’ll hit 3rd party CDNs anyway. Unless its coverage is 100℅, it’s less than useless for privacy as the hit pattern to CDNs might even make you stand out.
Good to know! I had it for data saving since I was on a metered connection, but that’s no longer the case. Will get rid of it. Might still be useful on Android though, no?
As for Privacy Badger, I mostly use it for getting rid of embedded widgets like those weird third-party comments on articles and such.
LocalCDN is a fork of Decentraleyes that still actively maintained and updated. But this kind of extension is getting less and less effective now that a huge proportion of websites minify and bundles their assets as part of their deployment process. For example, Lemmy uses Bootstrap but LocalCDN can’t replace it with local copy because Lemmy bundle their Bootstrap assets into minified js and css bundles.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
I’ve read not to bother with Decentraleyes. The dependencies are often out of date which mean you’ll hit 3rd party CDNs anyway. Unless its coverage is 100℅, it’s less than useless for privacy as the hit pattern to CDNs might even make you stand out.
Privacy Badger is also redundant if you have uBO.
Good to know! I had it for data saving since I was on a metered connection, but that’s no longer the case. Will get rid of it. Might still be useful on Android though, no? As for Privacy Badger, I mostly use it for getting rid of embedded widgets like those weird third-party comments on articles and such.
LocalCDN is a fork of Decentraleyes that still actively maintained and updated. But this kind of extension is getting less and less effective now that a huge proportion of websites minify and bundles their assets as part of their deployment process. For example, Lemmy uses Bootstrap but LocalCDN can’t replace it with local copy because Lemmy bundle their Bootstrap assets into minified js and css bundles.