What if Google decides that they will ignore that header? Is there anything preventing them from doing that? Do we know why they decided to even implement this "workaround" with header?
What if Google decides that they will ignore that header? Is there anything preventing them from doing that? Do we know why they decided to even implement this "workaround" with header?
For lots of people that’s not the case. Their work mandates which browser they can use, which is (partialy) why it took so long for IE to go away.
Is it an informed decision?
Most normal users use Chrome because "everyone else does", and won't even have a clue what FLoC is.
“Because it was installed on my machine bundled with some third-party software” is also a big factor (but obviously, nobody will give you this answer, because they don't even know where Chrome came from)
at least following cases would cause this:
(1) They are disliking tracking
(2) They are disliking Google
(3) Google is competing with them
(4) They want to be liked by people disliking tracking or Google
Potential privacy laws, competition, bad press,... but technically, nothing. Same as DoNotTrack.
In fact that's the whole idea behind FLoC. It is supposed to be a privacy improving feature! For now, the usual tracking methods based partly on third party cookies work for them, certainly better than FLoC would, and they are definitely more privacy invading.
But with things like GDPR, and with privacy being a bigger and bigger selling point, Google feels like it had to find something else and FLoC is their answer.
I don't know how the story will end but most likely in the same way as DoNotTrack, which started out badly, and turned into a joke when browsers started enabling it by default, disregarding the recommendation.