Discourse CDNs are blocked by privacy badger

riking · January 5, 2017, 1:36am

Oh, right. Hmmm… the v parameter maybe? That’d be a real pain if that’s what’s tripping it.

Here’s one of the relevant source files from last time I was investigating this stuff:

github.com/EFForg/privacybadgerfirefox-legacy

lib/heuristicBlocker.js

master


      
          const {
            checkPrivacyPolicy,
            whitelistHostFromPrivacyPolicy
          } = require("./policyCheck");
          const { doDependingOnIsPrivate } = require("./privateBrowsing");
          const prefs = require('sdk/simple-prefs').prefs;
          const pbUI = require("./ui");
          /**
           * originFrequency: A map of third party domains to the set of first party
           * domains where they have been observed making requests.
           *
           * blockedOrigins: The set of domains that are blocked from making third party
           * requests due to the heuristic.
           */
          const stored = [ "originFrequency",
                           "originFrequencyPrivate",
                           "blockedOrigins" ];
          
          // Initialize/cleanup persistent storage
          exports.init = function () {
            stored.forEach(function(store) {

Topic		Replies	Views
Defaulting to discourse.org CDN for avatars is a privacy and security risk Feature privacy	23	7375	December 4, 2025
Discourse & Cloudflare Installation	49	4823	January 26, 2024
Some sites are missing letter icons Bug	6	1735	August 15, 2017
Enable a CDN for your Discourse Self-Hosting cdn , configuring , how-to	72	293422	October 4, 2025
uMatrix browser add-on causes white pages when visiting Discourse instances Support	14	1349	April 6, 2021

Discourse CDNs are blocked by privacy badger

Related topics