Services/Shavar/Lists

Shavar Lists

Summary

The purpose of this wiki is to provide:

• A list-centric matrix of shavar dependencies.
  • intent is to easily view a match-up between lists and when they will appear in a specific version of the client as well as when they will be available from the shavar server itself.
• A Basic overview of list "pref sets" used for testing

Client-side

• What lists are currently being consumed by the client (in Nightly, DevEd, Beta, etc.)?
• What lists will be removed / added and when (and in what client version)

Server-side

• What lists are currently being server in STAGE, in PRODUCTION?
• What lists are to be removed (no longer served) and with what deployment?
• What lists are to be added (to be served) and with what deployment?

#top

List Dependency Matrix

list name	Server Deploy			Client Version		Comments (Ops/QA/Dev)
	Usage Env	Adding List(s)	Removing List(s)	Adding List(s)	Removing List(s)
mozfull-track-digest256	STAGE, PROD			Fx43
mozfullstaging-track-digest256	STAGE, PROD			N/A		Never shipped w/ FF
mozplugin-block-digest256	STAGE, PROD			Fx47
mozplugin2-block-digest256	STAGE, PROD			Fx47
mozpub-track-digest256	STAGE, PROD			Fx38	Fx42
mozstd-track-digest256	STAGE, PROD			Fx42
mozstd-trackwhite-digest256	STAGE, PROD			Fx42
mozstdstaging-track-digest256	STAGE, PROD			N/A		Never shipped w/ FF testing new entries before we submit them to Disconnect
mozstdstaging-trackwhite-digest256	STAGE, PROD			N/A		Never shipped w/ FF testing new entries before we submit them to Disconnect
moztestpub-track-digest256	STAGE			N/A		Never shipped w/ FF
moztestpub-trackwhite-digest256	STAGE			N/A		Never shipped w/ FF
base-track-digest256	STAGE, PROD
basew3c-track-digest256	STAGE, PROD
baseeff-track-digest256	STAGE, PROD
content-track-digest256	STAGE, PROD
contentw3c-track-digest256	STAGE, PROD
contenteff-track-digest256	STAGE, PROD

#top

List Testing - "Pref Sets"

For testing shavar and tracking protection client behavior (in the browser), we need to set certain custom preferences in about:config.

Below you will find a matrix of test "pref sets" and their usage

Pref Set	Key Feature	Comments
mozstd	determine what list client uses to block things
mozfull	tracking table pref - we switch the blacklist, keep same whitelist
mozstaging	for staging changes to the disconnect list
moztestpub	change white & blacklist because we those are the ones we can edit in github	should be called "editing-list" or "e2e-test". For all other tests, the actual underlying list is the disconnect one (except mozstaging which has another upstream repo)

#top

List Types

1. staging one
2. disconnect list
3. editing list

#top