Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 654
    • Issues 654
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 100
    • Merge requests 100
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #2630
Closed
Open
Issue created Apr 18, 2021 by Sean King@seankingDeveloper

Opt out of Google's FLoC

Google is starting to track site visitors even if such a site has zero relationships with Google Analytics. Though it is currently said that it's being tested on only a handful of Google Chrome users, we should prepare and treat this as a security concern.

Recently, Plausible Analytics has opted out and there is a proposal to do the same for WordPress.

Now, how to do this is pretty simple. We just set the following header: Permissions-Policy: interest-cohort=()

I'd imagine we just add setting that header to the webserver templates. Either that, or there's some clever way to set these headers from Pleroma. Who knows? IDK.

Assignee
Assign to
Time tracking