Does Google FLoC track your porn preferences using the ad blocking EasyList?
fungiboletus.github.io
fungiboletus.github.io
> FLoC can and will reveal sensitive information, we cannot surely prevent that because it's difficult, fuck you.
This is an inaccurate and frankly dishonest summary of the draft's CYA language stating that "sensitive" is impossible to define centrally in a way that's universally true, as the same info may be considered "sensitive" at different points in time to different people. In unambiguous cases, like porn, the draft states that sensitive visits are to be ignored by the browser. The author's response? "I tried glancing at the C++ code and I didn't see anything but it's big" (or in his parlance, "it's difficult, fuck you").
So to sum the article up:
1) a dishonest summary of FLOC's sensitive-content policy
2) a self-contradictory concession to the fact that FLOC does state how sensitive content should be handled
3) a lazy handwave about the code being hard to read so it _probably_ doesn't conform to the spec and is not planned to
4) A histrionic call to shut down FLOC
This is just the HN version of Breitbart or Huffington Post, outrage porn for those who don't care to actually inform themselves.
FLoC's draft does not offer a solution for sensitive information. It merely suggests a first step, filtering some obviously sensitive information, that is not implemented in the current experiment.
About the code I looked hard, and the fact that I couldn't find how sensitive information is handled by FLoC in an open-source implementation is interesting. Either it's not there, or it's very hidden which is not good either.
You didn't comment about using the community efforts to block ads to track people.
I'm sorry the post didn't match your expectations.