> Cross-origin requests in content scripts already encounter restrictions by advances of the web platform (e.g. SameSite cookies, CORP) and privacy features of Firefox (e.g. state partitioning). To support extensions, we are allowing extension scripts with sufficient host permissions to be exempted from these policies. Content scripts won’t benefit from these improvements, and will eventually have the same kind of permissions as regular web pages (bug 1578405). We will continue to develop APIs to enable extensions to perform cross-origin requests that respect the user’s privacy choices (e.g. bug 1670278, bug 1698863).
Does this mean Local CDN will potentially work better? It currently runs into these limitations a lot.
Privacy Badger ne sert strictement à rien et est redondant avec de bons filtres sur uBlock. HTTPS Everywhere est un peu pareil. Si un site n'utilise pas HTTPS en 2021, peut-être vaut-il mieux l'éviter.
Le blocage de scripts est un truc que peuvent faire tous les navigateurs nativement. Et de toute manière c'est se tirer une balle dans le pied. Mieux vaut utiliser LocalCDN et charger tous les frameworks habituels localement.
Found it! There were messages on the Console about CORS requests on some Cloudflare resources, which led me to LocalCDN which caches them. Turning it off fixed the issue, and so did turning it back on then enabling the "HTML filter" option on it. Will keep it in mind for the future, and now i know about backing up Ublock options. Thanks!
its really easier with a diagram tbh Locacdn is an alternative to decentral eyes and has thsi diagram https://www.localcdn.org/img/replacement.png
but tbh localCDN breaks a lot of sites.. Decentral eyes i had no issues with ever. so i would recommend to start with decentral eyes as you can install and completely forget about it