So after thinking a lot about FLOC and how it impacts and changes the advertisement environment, I have more questions than answers.
And at least from my current understanding, it becomes worse for organisations that want to advertise, which might includes your government trying to educate citizens about things, while not really making things much better for individual privacy, due to the ability to correlate cohort IDs to identify users.
While a lot of people decided to set a header to opt-out from FLOC tracking for their users, I decided to embrace it and let people make up their own mind.
For those interested in the banner, here are the implementation details:
It's kept simple and efficient. It'll only show up, when your browser implements the API. Enjoy!
I just realised that implicitly I built a FLOC tester :D
Want to check if your browser implements FLOC? Just go to https://shivering-isles.com and if a banner shows up warning you about FLOC, your browser is affected. Amazing!
Related: if you want to test if the detection works, you can use the following command in (Fedora) Linux with #chromium:
`chromium-browser "--user-data-dir=$(mktemp -d)" --enable-blink-features=InterestCohortAPI --enable-features="FederatedLearningOfCohorts:update_interval/10s/minimum_history_domain_size_required/1,FlocIdSortingLshBasedComputation,InterestCohortFeaturePolicy"
(It'll enable the feature in a temporary profile that is used until you terminate the command)
And it's done! A 💯% legitimate implementation of Google's FLoC standard for Firefox in an extension:
Finally we can have this awesome private ad company gift in a browser that is not chromium based!
And of course it's a completely serious and not at all satirical/sarcastic implementation. I swear!
Oh no! I'm so floced!
Needed to set my User-Agent to chromium for the scanner test to actually try it, but here we go. My extension works! And the best part, I'm in a new cohort on every page reload.
Finally I can use FLoC in Firefox! 🤡
GitHub Pages "blocks" Google's FLoC now by adding the opt-out header.
I don't think this is any reason to celebrate. #Google pulled two tricks here:
1. It identified all websites that are against this standard, making it easy to rank them worse.
2. Provided a technical solution to a social problem making all the tech elitist feel good by adding a header instead of protesting.
@sheogorath Agreed, but how do we protest against this?
Petition and pressure Google to roll back? EFF is already doing that, but I don't think Google is going to listen.
Artificially break your site on Chrome? Ask visitors to switch browsers? Even if there's a way of doing that without breaking Brave et al, I doubt enough people will be willing to do that.
Show a polite message without breaking the site? Most people will just dismiss it like they dismiss a cookie banner.
A generalist Mastodon instance with a nice domain name. Running on Glitch Social's fork with a custom theme!