uBlock Origin: Address first-party tracker blocking (github.com)

Article summary

The uBlock Origin issue tracker discusses the challenge of blocking first-party trackers that use techniques like CNAME records to bypass filters. These trackers can be difficult to detect and block, and may require new approaches to filtering. The discussion highlights the cat-and-mouse game between tracker providers and ad blockers. The uBlock Origin developer is considering new features to address this issue.

Main themes

• first-party tracking
• ad blocking
• tracker bypassing techniques
• CNAME records
• browser fingerprinting
• ad delivery innovation
• online privacy
• user tracking

What commenters say

• First-party tracking is not a significant concern as long as it does not correlate user identity across websites.
• First-party tracking can still be used to collect user data and correlate identities across websites, even if it requires more effort and resources.
• Blocking self-hosted, single-site tracking solutions like Piwik may be overly restrictive and penalize website owners who are trying to do the right thing.
• The use of CNAME records to bypass filters is a significant problem that requires new approaches to filtering.
• The effort to serve ads to users who block them may be more costly than the potential revenue.
• Ad-blocking has become more commonplace, driving advertisers to innovate and find new ways to get around it.
• The use of canvas or webassembly to deliver ads may be the next frontier in the arms race between ad blockers and advertisers.
• Browser fingerprinting and other tracking methods can still be used to correlate user identities across websites, even if first-party tracking is blocked.