Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Broken comments self-hosted by Free Software community #2257
What is your browser and browser version?
Chrome Version 71.0.3578.98
What is broken and where?
The https://pixls.us community runs a forum at https://discuss.pixls.us that also serves as the commenting back-end for multiple Free Software photography websites (pixls.us, darktable.org, digikam.org).
We (pixls.us) provide management of comments, forum, and community for various Free Software photography projects, and we use a Discourse forum as the backend for this. We basically provide an embed for forum topics to serve as comments on posts at each of these websites.
What is the "culprit" domain?
What is your debug output for this domain?
Following the instructions in Chrome yields nothing (ie:
On the darktable.org and digikam.org domains we embed forum topic posts from discuss.pixls.us at the bottom of certain posts to work as comments for the page. So if you look at the end of the page on a news post from those sites, you should see the embedded topic posts from discuss.pixls.us:
Those are examples of how the forum topics are embedded to act as comments. Does this help?
side note: the same method will be used for a few more projects in the near future as well!
Ah yes, thank you.
It looks like users who previously visited pixls.us directly have a Google Analytics cookie placed on
If your forum domains do not actually track users in any way, you could post the EFF DNT policy (https://www.eff.org/dnt-policy) on each domain (for example, https://discuss.pixls.us/.well-known/dnt-policy.txt) to tell Privacy Badger that domain is DNT compliant and should be left alone.
We are going to teach Privacy Badger to learn to block Google Analytics (#367) in a future update, which will avoid this entire class of problem in the future.
Privacy Badgers should no longer learn to block pixls.us going forward. However, anyone who already visited pixls.us directly and got the Google Analytics cookie will still teach their Privacy Badger about tracking by pixls.us whenever they come across pixls.us resources embedded on other sites. You could post the EFF DNT policy on each pixls.us domain (that gets used for embedding) to take care of those users, assuming these pixls.us domains are indeed compliant with the policy.