We'll add support for these tags in: * https://github.com/mozilla-services/shavar-prod-lists/pull/47 * https://github.com/mozilla-services/shavar-list-creation-config/pull/35 * https://github.com/mozilla-services/shavar-list-creation/pull/62 The only tags we are going to support at the moment are fingerprinting and cryptomining. I've tentatively named the new lists based on these categories: * base-fingerprinting-track-digest256 * content-fingerprinting-track-digest256 * base-cryptomining-track-digest256 * content-cryptomining-track-digest256 Where the `base-*` lists are pulled from domains on the Advertising, Analytics, Social, and Disconnect top-level categories. The `content-*` lists only pull from the Content category, and are currently empty (i.e., there are no tagged domains in those categories).
New lists are added by: 1) Creating a source repo for them and configuring them in the list-creation script configs (https://github.com/mozilla-services/shavar-list-creation-config) 2) Once that's complete and working appropriately, you will need to create a server config for the relevant deployment domain. Start with stage. (https://github.com/mozilla-services/shavar-server-list-config) 3) Having done that, and tested in stage, you can create the prod config. Unfortunately, this step requires manual intervention for activation, however, the new list creation *should* actually test the code landed and running in stage to "automatically" pick up new lists. In this *one* case, I will need to deploy a new version of shavar for this to happen in -prod.
(1) is done and merged via https://github.com/mozilla-services/shavar-list-creation/pull/62, https://github.com/mozilla-services/shavar-prod-lists/pull/47, and https://github.com/mozilla-services/shavar-list-creation-config/pull/35. (2) is done in https://github.com/mozilla-services/shavar-server-list-config/pull/19, but we'll hold off on merging that until everyone is back next week to go through testing on stage.
Is there a reason to bundle categories into the base-* lists instead of offering them based on the Disconnect categories? We've already split up the original base-track lists in bug 1425075 to allow for a clear category-based settings API in GeckoView. I fear that we would have to do the same procedure again for each bundle lists we add to maintain consistency.
We'd like the option to block or apply restrictions only to domains that contain one of the category tags. Thus, we want to created separate lists for each tag that don't include non-tagged domains from the top-level categories (e.g., Analytics, etc). Note that the ads/analytics/etc lists will still contain the domains that have tags, so the creation of these new lists won't impact those. I don't see a use case where we'd want to further split the lists. E.g., domains in the top-level ads category that have the fignerprinting tag, and domains in the top-level Social category that have the cryptomining tag. It's technically possible to do. Is this something you'd like to support?
Flags: needinfo?(senglehardt) → needinfo?(esawin)
Commits pushed to master at https://github.com/mozilla-services/shavar-list-creation-config https://github.com/mozilla-services/shavar-list-creation-config/commit/d5c19916e3e9056d42268fb07da5353799dcd96e bug #1515806 - cryptomining and fingerprinting lists https://github.com/mozilla-services/shavar-list-creation-config/commit/584336ad13a9b7260ee26768789e5847f2c48b0e Merge pull request #37 from mozilla-services/cryptomining-and-fingerprinting-lists-1515806 bug #1515806 - cryptomining and fingerprinting lists
Commits pushed to master at https://github.com/mozilla-services/shavar-server-list-config https://github.com/mozilla-services/shavar-server-list-config/commit/95baba589a050b3e4e193682c97c394cf3e5ee00 bug 1515806 - serve cryptomining and fingerprinting lists https://github.com/mozilla-services/shavar-server-list-config/commit/0a57c24246d82dc8c7619eefc995a6154c570c2d Merge pull request #20 from mozilla-services/serve-cryptomining-and-fingerprinting-lists-1515806 bug 1515806 - serve cryptomining and fingerprinting lists
Status: NEW → UNCONFIRMED
Ever confirmed: false
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Commits pushed to master at https://github.com/mozilla-services/shavar-server-list-config https://github.com/mozilla-services/shavar-server-list-config/commit/d50ac07c4a8575b725c0d587a0d0cb549598d4f0 bug 1515806 - fix CM and FP lists redirect_url_base https://github.com/mozilla-services/shavar-server-list-config/commit/fb8d85f73c033435051190051bd53917eddaf047 Merge pull request #23 from mozilla-services/fix-cryptomining-and-fingerprinting-configs-1515806 bug 1515806 - fix CM and FP lists redirect_url_base
You need to log in before you can comment on or make changes to this bug.