Closed Bug 1530080 Opened 7 years ago Closed 6 years ago

Fingerprinting and Cryptomining Breakage Study

Categories

(Data Science :: Experiment Collaboration, task)

x86_64
macOS
task
Not set
normal
Points:
3

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: arthur, Assigned: flawrence)

References

Details

Brief Description of the request: We want to investigate the breakage caused by fingerprinting and cryptomining blocking.

Any timelines for the request or how this fits into roadmaps:
We hope to run this test during April (Firefox 66), with time for analysis and a a go/no-go for shipping these protections in 68.

Links to any assets (e.g Start of a PHD, BRD; any document that helps describe the project):
Draft of PHD: https://docs.google.com/document/d/1nYHgxro-YLNv5Ruvzd22d1mc4gC1Ti7Y9fYWki096BM/edit

This will be similar to a current add-on breakage study, that turns on Cookie Restrictions for the Basic list and collects breakage reports: https://experimenter.services.mozilla.com/experiments/cookie-restrictions-blocking-breakage/

Description of Basic and Strict Tracking Protection lists: https://docs.google.com/document/d/1yvLLVUS5Bs29a20m2INz2Wt47YB8lO6UvR-jSyslFl4/edit

Current fingerprinting and cryptomining lists (see the “Cryptomining” category and domains with the “fingerprinting” tag). These lists will be expanded prior to the study starting. https://github.com/mozilla-services/shavar-prod-lists/blob/8caa4d2f8fad411c837d74666df6ec19f48c42f1/disconnect-blacklist.json

Name of Data Scientist (If Applicable):
We would like to request flawrence

Assignee: nobody → flawrence
Status: NEW → ASSIGNED
Points: --- → 3

Fairly sure that this got replaced by bug 1533778 and bug 1562545.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.