Add more JS-based first-party tracking to encourage uBlock Origin to be able to block it

Release notes

uBlock Origin won't add blocking for first-party tracking done by self-hosted applications, adding first-party tracking to self-hosted applications is the best way to make uBlock Origin add blocking for first-party tracking done by self-hosted applications.

Problem to solve

uBlock Origin can't block first-party tracking by self-hosted web applications, such as hypothetical first-party tracking done by GitLab.

Intended users

Non-GitLab users.

User experience goal

The user should be annoyed at uBlock Origin for not being able to block such self-hosted first-party trackers. The hoster should gain more knowledge about their users.

Proposal

Adding first-party trackers to self-hosted GitLab would encourage uBlock Origin developers to figure out a way to block said trackers.

Further details

Permissions and Security

Unknown.

Documentation

Tracking must be documented, and needs to show up on terms of service/privacy policy, as well as be opted-in through an in-page-pop-up.

Availability & Testing

What does success look like, and how can we measure that?

Success can be measured when uBlock Origin adds application-based in addition to domain-based blocking. Acceptance criteria is basically whether the in-page-pop-up works and whether the data gets collected when opted-in.