The company recently announced that it was rolling out a new HTTP header for all sites created in GitHub Pages. In an extremely short blog post, the company provided further details on the new HTTP header, saying:
“All GitHub Pages sites served from the github.io domain will now have a Permissions-Policy: interest-cohort=() header set. Pages sites using a custom domain will not be impacted.”
We're looking at how our readers use VPN for a forthcoming in-depth report. We'd love to hear your thoughts in the survey below. It won't take more than 60 seconds of your time.
- We've built a list of the best VPN services available
- These are the best anonymous browsers on the market
- Also check out our roundup of the best proxy
The only indication that this new HTTP header has something to do with FLoC is the inclusion of the word cohort. FLoC itself stands for Federated Learning of Cohorts and this new advertising technology was developed by Google to replace third-party cookies for ad tracking through a new API.
Blocking FLoC's cohorts
In addition to disabling FLoC in GitHub Pages, GitHub's main website also now uses this new HTTP header according to BleepingComputer. This means that the company doesn't want its users to be added to Google's cohorts when they visit its website.
While FLoC is now rolling out to a small percentage of users in Australia, Brazil, Canada, India, Indonesia, Japan Mexico, New Zealand, the Philippines and the US, you can use the Electronic Frontier Foundation's (EFF) AMIFloced site to check if you have been issued a FLoC ID and added to one of Google's cohorts.
Although we've yet to hear from Google regarding whether or not its roll out of FLoC has been a success yet, so far Brave, Vivaldi, the EFF, DuckDuckGo and WordPress have all openly voiced their concerns surrounding this new advertising technology.
- We've also highlighted the best business VPN