faster way to tell which trackers are required for content
Posted: Sun Sep 18, 2016 11:01 pm
I've use NoScript for several yrs. The number of trackers on typical pages has grown exponentially.
Is there any way to speed up determining which trackers control what on individual pages, as they change from month to month? Whether on the 1st or nth time you visit a site? The base domain appended with "cdn" is easy enough. Some trackers you learn aren't required. It occurs that the constant changing could partly be intended to make using NoScript & other extensions a nuisance, so more users will stop using them.
On many pages, the trackers providing a specific feature or content changes often. It changes from month to month on several sites, which tracker controls what - it becomes a perpetual guessing game.
Even if they don't continually change on site A, the specific content or features controlled by say, the same tag manager, may not control the same things on site B. It's highly variable from site to site. At times, some sites - like big news media sites won't work in Firefox even if all trackers are allowed in NS, cookies are allowed & no other privacy or security extensions are active.
You can allow trackers one by one or possibly view the page source - for a hint on which tracker is associated with specific content you're interested in. Either method is very time consuming.
Or temporarily allow all on a page - not the best idea on untrusted sites. Doing technical research & visiting dozens of unknown sites, these methods become unacceptably slow.
Incidentally, I join others that complain about this forum's software spam filter being hay wire - giving the message, "Ooops, something in your posting triggered my antispam filter." On this post, after long time trying to find the issue, I think it was just mentioning names of common trackers in my post. Not in ads or spam like way.
Is there any way to speed up determining which trackers control what on individual pages, as they change from month to month? Whether on the 1st or nth time you visit a site? The base domain appended with "cdn" is easy enough. Some trackers you learn aren't required. It occurs that the constant changing could partly be intended to make using NoScript & other extensions a nuisance, so more users will stop using them.
On many pages, the trackers providing a specific feature or content changes often. It changes from month to month on several sites, which tracker controls what - it becomes a perpetual guessing game.
Even if they don't continually change on site A, the specific content or features controlled by say, the same tag manager, may not control the same things on site B. It's highly variable from site to site. At times, some sites - like big news media sites won't work in Firefox even if all trackers are allowed in NS, cookies are allowed & no other privacy or security extensions are active.
You can allow trackers one by one or possibly view the page source - for a hint on which tracker is associated with specific content you're interested in. Either method is very time consuming.
Or temporarily allow all on a page - not the best idea on untrusted sites. Doing technical research & visiting dozens of unknown sites, these methods become unacceptably slow.
Incidentally, I join others that complain about this forum's software spam filter being hay wire - giving the message, "Ooops, something in your posting triggered my antispam filter." On this post, after long time trying to find the issue, I think it was just mentioning names of common trackers in my post. Not in ads or spam like way.