On Wed, Apr 28, 2021 at 10:59 AM Oleg Nenashev <[email protected]> wrote:
> Yesterday GitHub set a good precedent by disabling FLoC by default > <https://github.blog/changelog/2021-04-27-github-pages-permissions-policy-interest-cohort-header-added-to-all-pages-sites/>. > I think we should do the same. > Could you explain in what way this header does anything for us, in particular *in Jenkins*? IIUC, it globally limits what elements on a page are allowed to do, similar to Content-Security-Policy. In this case, it makes the JS call document.interestCohort() not do track-y things. This makes sense for GitHub pages, as they let folks host their own content there. But if jenkins.io or Jenkins load content that does this, we should just put an end to that. What am I missing? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKanSdbMpMRS4x2sximOiGOfxuy1acSEKj2k6DMMvqG-Q%40mail.gmail.com.
