• Spotlight7573@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 months ago

    It’s part of the open source chromium engine.

    Here’s how it implements some of the privacy sandbox stuff for example: https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/components/privacy_sandbox/

    and here’s some of the Topics API stuff: https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/components/browsing_topics/

    Theoretically they could still inject malicious code even if the stuff in the chromium source code looks fine. Given they got sued for their servers still tracking you while Chrome was in Incognito mode (even with the warning every time you open Incognito mode), I’d imagine any injection of code like that would result in another lawsuit (or several). At some point you either have to trust that Google is implementing things how they say they are in the code that they put out or just use a different browser.

    • le_saucisson_masquay@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      I checked your link but as most people I’m not programmer, so we can’t check or even remotely understand what Google engineers does. On the other hand, what common people can understand is 'follow the money ́. Google makes most of its money on selling personalized ads, the more data they get on you the higher advertiser will bid.

      It would make absolutely no sense, financially, for Google to reduce it’s tracking ability and let the user decide which ad they want to see or not.

      And at the end Google is a business, money goes in, more money goes out. They could be doing what they claim to do right now, only to change in 2 years when all third party advertiser are bankrupt because they can’t use cookies anymore. That’s another possibility.