A user reports that Boing Boing is not rendering properly in Firefox due to browser extensions. After testing in private browsing mode with fewer extensions, the site loads correctly. The user identifies errors in the browser console related to missing assets, such as a 404 error for a JavaScript file from the Discourse CDN. Falco suggests that an extension is blocking the domain at the DNS level, likely Privacy Badger, referencing a known issue. Lascaux confirms that disabling Privacy Badger and restarting Firefox resolves the problem, indicating the extension was the cause.
I think maybe one of my extensions is causing BoingBoing to not render? If I open the BBS in Firefox, where I have it in it’s own container + multiple privacy extensions, it doesn’t load.
Opening in private browsing (where only ublock and noscript are enabled) renders fine.
I took a screenshot of all the extensions I have, open to suggestions on tweaks.
[Edit: it was privacy badger]
Really odd it just randomly started doing that, I haven’t tweaked my browser settings recently
Could have been an extension update or a Discourse update that clashes with an extension… if you disable each extension one-by-one and refresh the page you can find the specific culprit.
If you right click and select inspect element, do you see any errors in the console tab?
So one of your extensions is blocking this domain at the DNS level. I’d guess it’s “Privacy Badger”, as it has done this many times before: Discourse CDNs are blocked by privacy badger