[meta] ETP breakage for webpages that have Disqus comment section
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox123 | --- | affected |
People
(Reporter: rbucata, Unassigned)
References
(Depends on 2 open bugs, Blocks 9 open bugs)
Details
(Keywords: meta)
This is a meta for tracking ETP issues that occur on all web pages that have Disqus comments enabled
Issue observed:
The Disqus comment section is not visible
Comment 1•10 months ago
|
||
Is it worth creating separate bugs for every site? Looks like a general Disqus problem? In the last days I have surfed some camera rumors blogs, where Disqus seems to be a favorite way to handle comments. Comment sections failed on all the sites that are using Discus:
https://photorumors.com/
https://www.mirrorlessrumors.com/
https://www.canonnews.com/
https://nikonrumors.com/
https://sonyaddict.com/
https://www.sonyalpharumors.com/
https://www.fujirumors.com/
https://www.43rumors.com/
https://www.l-rumors.com/
https://pentaxrumors.com/
https://leicarumors.com/
But thinking about how "infected" comments can be on such sites, some might actually consider it being a plus that comments can't be seen ;-)
Is it worth creating separate bugs for every site?
Thanks for asking but no, this is general problem because Disqus is part of Disconnect list.
Comment 3•10 months ago
|
||
(In reply to Dan Mehic from comment #2)
Is it worth creating separate bugs for every site?
Thanks for asking but no, this is general problem because Disqus is part of Disconnect list.
And maybe there's a good reason it is?
But I notice behavior is inconsistent. Sometimes it works, other times not. Right now Disqus seems to work on the sites I visit.
Comment 4•10 months ago
|
||
It's unfortunate that there is no functionality to add exceptions for individual trackers. Instead, if we want this to work, we have to turn off tracking content blocking completely. I think the ideal functionality would be to open the tracking protection door hanger, expand the tracking content, then have buttons on each one listed to allow that tracker on the currently loaded domain. That would allow you to enable functionality that is blocked while still blocking other tracking content. It would also still block that tracker on other domains, so it wouldn't be able to track you everywhere and just on the domains you explicitly allow. I don't know how difficult that would be to implement though.
Comment 5•9 months ago
|
||
(In reply to Matt Cosentino from comment #4)
It's unfortunate that there is no functionality to add exceptions for individual trackers.
Actually, Today I Learned that you can create a preference for host names of servers you want to bypass the standard lists (urlclassifier.trackingSkipURLs
). See:
- https://support.mozilla.org/en-US/questions/1440102#answer-1637316
- Based on: https://support.mozilla.org/en-US/questions/1434798#answer-1626216
In the absence of a UI to populate this preference from the blocked trackers list, or anywhere else, it is very difficult for users to take advantage of this feature.
Thanks for the feedback everyone. We're exploring ways for users to easily enable blocked content without disabling ETP altogether.
Comment 7•8 months ago
|
||
(In reply to jscher2000 from comment #5)
Actually, Today I Learned that you can create a preference for host names of servers you want to bypass the standard lists (
urlclassifier.trackingSkipURLs
).
As a general solution for disqus.com, this seems to work for all sites I have visited:
urlclassifier.trackingSkipURLs = disqus.com,*.disqus.com
Comment 8•8 months ago
|
||
(In reply to jscher2000 from comment #5)
(In reply to Matt Cosentino from comment #4)
It's unfortunate that there is no functionality to add exceptions for individual trackers.
Actually, Today I Learned that you can create a preference for host names of servers you want to bypass the standard lists (
urlclassifier.trackingSkipURLs
). See:
- https://support.mozilla.org/en-US/questions/1440102#answer-1637316
- Based on: https://support.mozilla.org/en-US/questions/1434798#answer-1626216
In the absence of a UI to populate this preference from the blocked trackers list, or anywhere else, it is very difficult for users to take advantage of this feature.
Thanks, that does help. It bypasses the list on all sites though, so it could track me on sites I don't want it to. In the case of disqus, they use different subdomains on each site, so I can add them individually and that's good. But, there's one site I use that has a poll feature using polldaddy.com that is marked as a tracker. Being able to whitelist it only on that site would allow the content to work where I want it to work and not track me anywhere else.
Comment 9•6 months ago
|
||
The urlclassifier.trackingSkipURLs workaround doesn't seem to work anymore.
Comment 10•6 months ago
|
||
(In reply to Matt Cosentino from comment #9)
The urlclassifier.trackingSkipURLs workaround doesn't seem to work anymore.
It looks like you now need to add c.disquscdn.com
as well.
As a research strategy, you can open the Web Console (Ctrl+Shift+K, or on Mac, Command+Alt+K) and filter on content blocking -- for example:
The resource at “https://c.disquscdn.com/next/embed/lounge.load.8d3c7bf4ef0effbad0b35e184b729823.js” was blocked because content blocking is enabled.
Some others are blocked as well, but they seem related to advertising and not essential.
Comment 11•6 months ago
|
||
(In reply to jscher2000 from comment #10)
(In reply to Matt Cosentino from comment #9)
The urlclassifier.trackingSkipURLs workaround doesn't seem to work anymore.
It looks like you now need to add
c.disquscdn.com
as well.As a research strategy, you can open the Web Console (Ctrl+Shift+K, or on Mac, Command+Alt+K) and filter on content blocking -- for example:
The resource at “https://c.disquscdn.com/next/embed/lounge.load.8d3c7bf4ef0effbad0b35e184b729823.js” was blocked because content blocking is enabled.
Some others are blocked as well, but they seem related to advertising and not essential.
I did look through the web console and that wasn't there. I added it to my list anyway and they still didn't load. I then looked through all the other content being blocked, enabling one by one to see if it would fix anything, and I found that adding *.spot.im to the list fixed it. Aha! Turns out the site switched to using spot.im a while ago (oops, my bad) but they also still load disqus content for some reason. Before, just having 9to5googleprod.disqus.com in the list allowed them to be loaded, but now it seems spot.im is being blocked too.
Comment 12•5 months ago
|
||
I was experiencing the same issue, but had no idea it was related to Firefox, so I reported to Betterfox — as I thought it could be because of my hardening Firefox — and the creator said: "it seems Firefox still marks Disqus as Tracking even after adding an exception"
So, to give more context, here is my issue report linked to their comment: https://github.com/yokoffing/Betterfox/issues/293#issuecomment-2168273108
Comment 13•4 months ago
|
||
Dupes:
Bug 1869326
Bug 1872855
Bug 1874855
Bug 1884676
Bug 1905920
Maybe Mozilla could have fixed the bug faster or marked it as WONTFIX not to look so bad.
Description
•