Top Related Projects
Quick Overview
DuckDuckGo's Tracker Radar is an open-source project that provides a comprehensive dataset of web trackers. It aims to enhance online privacy by identifying and cataloging trackers across the internet. The repository contains regularly updated data about trackers, their prevalence, and their behaviors.
Pros
- Extensive and regularly updated dataset of web trackers
- Open-source, allowing for community contributions and transparency
- Provides valuable information for privacy-focused research and development
- Includes detailed metadata about trackers, such as categories and ownership
Cons
- May require significant processing power to analyze the full dataset
- Could become outdated quickly due to the rapidly changing nature of web tracking
- Might not capture all trackers, especially newer or less common ones
- Requires technical knowledge to fully utilize and interpret the data
Code Examples
This project is primarily a dataset rather than a code library, so code examples are not applicable.
Getting Started
While this is not a code library, you can get started with the Tracker Radar dataset by following these steps:
-
Clone the repository:
git clone https://github.com/duckduckgo/tracker-radar.git
-
Navigate to the cloned directory:
cd tracker-radar
-
Explore the data files in the
domains
andentities
directories. -
Use tools like
jq
or Python'sjson
module to parse and analyze the JSON data files. -
Refer to the README.md file for detailed information about the data structure and contents.
Competitor Comparisons
Resources for uBlock Origin, uMatrix: static filter lists, ready-to-use rulesets, etc.
Pros of uAssets
- More comprehensive and frequently updated filter lists
- Community-driven development with active user contributions
- Supports a wider range of content blocking scenarios
Cons of uAssets
- May require more manual configuration for optimal performance
- Can potentially cause website breakage due to aggressive blocking
- Larger file size and memory footprint
Code Comparison
uAssets:
||example.com^$third-party
||analytics.example.com^
||ads.example.com^$script,image
Tracker Radar:
{
"domain": "analytics.example.com",
"categories": ["Analytics"],
"prevalence": 0.1
}
Key Differences
- uAssets focuses on filter rules for content blocking
- Tracker Radar provides structured data about trackers
- uAssets is primarily used by uBlock Origin, while Tracker Radar is used by DuckDuckGo and can be integrated into various privacy tools
Use Cases
- uAssets: Ideal for users seeking granular control over content blocking
- Tracker Radar: Better suited for privacy research and building comprehensive tracking protection systems
Community Engagement
- uAssets: Active community with frequent contributions and discussions
- Tracker Radar: Maintained by DuckDuckGo team with some community input
Update Frequency
- uAssets: Multiple updates daily
- Tracker Radar: Less frequent updates, typically monthly or quarterly
EasyList filter subscription (EasyList, EasyPrivacy, EasyList Cookie, Fanboy's Social/Annoyances/Notifications Blocking List)
Pros of EasyList
- Larger community-driven project with more frequent updates
- Broader coverage of ad-blocking rules, including both trackers and general ads
- Widely adopted and supported by many ad-blocking tools and browsers
Cons of EasyList
- Less focused on privacy-specific tracking
- Can be more complex to maintain due to its broad scope
- May cause more false positives due to aggressive blocking rules
Code Comparison
EasyList:
||example.com^$third-party
@@||example.com/ads.js|
.com/banner/$image
Tracker Radar:
{
"domain": "example.com",
"categories": ["advertising"],
"prevalence": 0.1
}
EasyList uses a syntax specific to ad-blocking, while Tracker Radar uses JSON to describe trackers and their properties. EasyList focuses on blocking specific URLs or elements, whereas Tracker Radar provides metadata about tracking domains.
Both repositories aim to improve user privacy and reduce unwanted content, but they approach the problem differently. EasyList is more suitable for general ad-blocking, while Tracker Radar is tailored for identifying and categorizing tracking domains. The choice between them depends on the specific use case and desired level of granularity in blocking or identifying trackers.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
DuckDuckGo Tracker Radar
This is not a block list, but a data set of the most common third party domains on the web with information about their behavior, classification and ownership. It allows for easy custom solutions with the significant metadata it has for each domain: parent entity, prevalence, use of fingerprinting, cookies, privacy policy, and performance. The data on individual domains can be found in the domains directory.
Related Resources
-
Read our blog post for more information on the Tracker Radar
-
To learn more about the Tracker Radar data format, see Data Model
-
The code used to build the Tracker Radar: Tracker Radar Collector and Tracker Radar Detector
Licensing
Copyright (c) 2020 Duck Duck Go, Inc.
The Tracker Radar data is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. If you'd like to license the list for commercial use, please reach out.
Questions
-
Questions about the Tracker Radar? See our frequently asked questions
-
Need help with other DuckDuckGo things? See DuckDuckGo Help Pages.
Top Related Projects
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot