Fenix: FNX3-17121 ⁃ Social Tracking Protection

[vesta0]

This ticket is about providing user with the option to enable social media tracking protection (the SOCIAL list from the TrackingProtectionPolicy) as part of the STRICT settings. The next iteration (once new Social Tracking Protection list that desktop is using is ready) will be to switch to using the new list by default as part of the recommended setting (separate ticket will be filed).

User Story

As a user, I want my browser to provide the option of blocking subresources from social media domains, so I have the choice to not be tracked by social media sites

Requirements:
Expose Disconnect social tracker list (socialtrack-digest256) as part of the Strict list
-Not enabled by default

Acceptance Criteria

• I can block social media trackers by enabling strict settings
• Social media trackers are not blocked by default.

[Amejia481]

@vesta0 I'm putting on hold until we research about how we want to approach this feature, across other platforms

[liuche]

@Amejia481 I'm looking at putting this into the next Fenix sprint or two, could you tell me a little more about what kind of research is still remaining? Or just waiting for UX designs?

[Amejia481]

I'm not completely sure how we are going to approuch this from the AC API, I will open bug on ac for that. As mock-ups are almost done, I think we can move forward from the Fenix side.

[Amejia481]

For activating blocking social trackers (as it's now) you just have to make sure that
SOCIAL is part of the TrackingProtectionPolicy that you are setting. If you are using recommended(). SOCIAL is already there.

const val RECOMMENDED = AD + ANALYTICS + SOCIAL + TEST + SAFE_BROWSING_ALL

[vesta0]

@Amejia481 and @AmyYLee @ekager I updated the description with a proposal of how to tackle Social Tracking Protection for now while we wait for the new list to be exposed in GV. Let me know what you think.

[Amejia481]

Great! @vesta0 Is there a bug for the GV team to expose the new list?

[vesta0]

That is a good question for @bifleming and @cpeterso

[cpeterso]

I filed a new GV bug to expose the Social Tracking Protection list: https://bugzilla.mozilla.org/show_bug.cgi?id=1568295

[bifleming]

Vesta, do we have a Fenix story that we can tie the GV bug to?

EDIT: Fenix story once GV has been landed: #4277

On Tue, Jul 23, 2019 at 12:26 PM Chris Peterson [e-mail]
wrote:

I filed a new GV bug to expose the Social Tracking Protection list:
https://bugzilla.mozilla.org/show_bug.cgi?id=1568295

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mozilla-mobile/fenix/issues/3571?email_source=notifications&email_token=ALLADYGX5Z4XOVGKV2JGJF3QA5LO5A5CNFSM4HZQRLDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UFSSY#issuecomment-514349387,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALLADYAX5DV5622D5RV2GS3QA5LO5ANCNFSM4HZQRLDA
.

--
Regards,
Betty

---

Betty Fleming | [email protected] | Engineering Program Manager, Firefox
Mobile

[liuche]

Two options:
1) Remove the social section until the new list is ready
1) Use basic Social list (which breaks some things) but remove from Recommended (so it's not turned on by default)

and then we can match Desktop once we get this new list, which is #4277 .
(Does iOS have this same problem?)

[cpeterso]

Dylan landed the new Disconnect social tracker list (social-track-digest256) in GV 70 Nightly. We don't plan to uplift the social tracker list to GV 69 because GV 70 Nightly will ride to GV Beta next week (September 3).

https://bugzilla.mozilla.org/show_bug.cgi?id=1568295

[Amejia481]

This will be covered on ac on this issue https://github.com/mozilla-mobile/android-components/issues/4213

[Amejia481]

Fenix is already using the new Mozilla social list and additionally we aligned our defaults with Desktop https://github.com/mozilla-mobile/android-components/issues/4349

[ekager]

The new aligned lists are now in master and will go out in the next release as well. There is no more work for Fenix to do here, so I am closing this ticket