I have been reading up on Chrome’s new Topics API and FLoC. Can someone explain to me why it is bad? Do the negatives of FLoC also apply to Federated Learning? (I’m not saying that FLoC is good, I’m just confused.)

  • @[email protected]
    link
    fedilink
    191 year ago

    It’s yet another scheme to gather data about Chrome users for the benefit of advertisers. Aside from the fundamental problems with that whole idea which people most often point to, it’s also underhanded in a way that cookies, tracking scripts, and browser fingerprinting aren’t: It’s code that’s built in to the web browser itself which exists for no purpose other than to act directly against the interests of its users. It may be the first time that’s happened in such an obvious and unambiguous way.

  • @mvirts
    link
    141 year ago

    Federated learning as a machine learning topic is unrelated to floc afaict.

    The issue I have with things like FloC and the topics API are that they are attempts to keep the cash flowing at Google before disabling 3rd party cookies, when it seems obvious that the time to disable 3rd party cookies is now.

    • @tester1121OP
      link
      English
      31 year ago

      So the features on my Pixel that use federated learning don’t share the same privacy risks as FLoC?

      • @mvirts
        link
        11 year ago

        I think not? I’m sure it still comes with some privacy risks, plus your phone is using power you paid for to train models owned by someone else I believe. What features are you thinking of? Lol I use a pixel as well

  • @[email protected]
    link
    fedilink
    41 year ago

    I think this is a pretty good breakdown and worth a read. Some key takeaways are that with FLoC Google would be able to track visitors to your website even if you were not using Google Analytics, and that the mechanism is built-in the Chrome browser so entirely controlled by Google.

    Here is a related article about Topics, the FLoC replacement.