• Dave@lemmy.nz
    link
    fedilink
    English
    arrow-up
    156
    ·
    2 months ago

    The problem is that a website is generally not served from one domain.

    Put a Facebook like button on your website, it’s loaded directly from Facebook servers. Now they can put a cookie on your computer with an identifier.

    Now every site you visit with a Facebook like button, they know it was you. They can watch you as you move around the web.

    Google does this at a larger scale. Every site with Google ads on it. Every site using Google analytics. Every site that embeds a Google map. They can stick a cookie in and know you were there.

      • Dave@lemmy.nz
        link
        fedilink
        English
        arrow-up
        58
        ·
        2 months ago

        Yes, it’s the reason for the tracking. To sell more targeted ads.

        If you’re up for reading some shennanigans, check out the book Mindf*ck. It’s about the Cambridge Analytica scandal, written by a whistleblower, and details election manipulation using data collected from Facebook and other public or purchased data.

    • MonkderVierte@lemmy.ml
      link
      fedilink
      English
      arrow-up
      17
      ·
      edit-2
      2 months ago

      Put a Facebook like button on your website, it’s loaded directly from Facebook servers. Now they can put a cookie on your computer with an identifier.

      Which is not allowed by GDPR btw, because they do that even if you don’t click them. There are plenty guides online, how to create your own, not tracking, facebook like button.

      • Dave@lemmy.nz
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 months ago

        How does GDPR fit in to Google Analytics and personalised ads?

        I would have thought it went something like: random identifier: not linked to personal info, just a collection of browsing history for an unidentified person, not under GDPR as not personal info.

        Link to account: let them request deletion (or more specifically, delinking the info from your account is what Facebook lets you do), GDPR compliant.

        Both Google and Facebook run analytics software that tracks users. I presume letting people request deletion once it’s personally linked to them is probably what let’s them do it? But I don’t live in a GDPR country, so I don’t know a whole lot about it.

        • MonkderVierte@lemmy.ml
          link
          fedilink
          English
          arrow-up
          5
          ·
          2 months ago

          No, it should’ve been opt-in. But loophole with “vital interest” and politics being slow and surface-level like politics.

      • Dave@lemmy.nz
        link
        fedilink
        English
        arrow-up
        42
        ·
        2 months ago

        It doesn’t have to be. Your browser sends the cookies for a domain with every request to that domain. So you have a website example.com, that embeds a Facebook like button from Facebook.com.

        When your browser downloads the page, it requests the different pieces of the page. It requests the main page from example.com, your browser sends any example.com cookies with the request.

        Your browser needs the javascript, it sends the cookie in the request to get the JavaScript file. It needs the like button, it sends a request off to Facebook.com and sends the Facebook.com cookies with it.

        Note that the request to example.com doesn’t send the cookies for Facebook.com, and the request to Facebook.com doesn’t send the cookie for example.com to Facebook. However, it does tell Facebook.com that the request for the like button came from example.com.

        Facebook puts an identifier in the cookie, and any request to Facebook sends that cookie and the site it was loaded on.

        So you log in to Facebook, it puts an identifier in your cookies. Now whenever you go to other sites with a Facebook like button (or the Facebook analytics stuff), Facebook links that with your profile.

        Not logged in? Facebook sets an identifier to track you anyway, and links it up when you make an account or log in.

        • intensely_human@lemm.ee
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 months ago

          How is Facebook able to know what site is requesting it? Is it in the referer header, or is it parameters in the javascript/image url?

          • Dave@lemmy.nz
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 months ago

            There is a referer header sent, but depending on the exact code added to the page, it’s very likely they are loading a snippet of JavaScript that lets them collect other information and trigger their own sending of information to their server.

            For example, Google Analytics has javascript added to the page, but loading fonts from Google’s CDN (which many sites do) will rely on the referer.