• ArchRecord@lemm.ee
    link
    fedilink
    English
    arrow-up
    298
    ·
    22 days ago

    For those who don’t care to read the full article:

    This basically just confines any cookies generated on a page, to just that page.

    So, instead of a cookie from, say, Facebook, being stored on site A, then requested for tracking purposes on site B, each individual site would be sent its own separate Facebook cookie, that only gets used on that site, preventing it from tracking you anywhere outside of the specific site you got it from in the first place.

    • peopleproblems@lemmy.world
      link
      fedilink
      English
      arrow-up
      196
      arrow-down
      2
      ·
      22 days ago

      Hahahahaha so it doesn’t break anything that still relies on cookies, but neuters the ability to share them.

      That’s awesome

      • ripcord@lemmy.world
        link
        fedilink
        English
        arrow-up
        53
        ·
        edit-2
        22 days ago

        Honestly, I thought that’s how it already worked.

        Edit: I think what I’m remembering is that you can define the cookies by site/domain, and restrict to just those. And normally would, for security reasons.

        But some asshole sites like Facebook are cookies that are world-readable for tracking, and this breaks that.

        Someone correct me if I got it wrong.

        • ArchRecord@lemm.ee
          link
          fedilink
          English
          arrow-up
          28
          ·
          22 days ago

          Total Cookie Protection was already a feature, (introduced on Feb 23st 2021) but it was only for people using Firefox’s Enhanced Tracking Protection (ETP) on strict mode.

          They had a less powerful third-party cookie blocking feature for users that didn’t have ETP on strict mode, that blocked third party cookies on specific block lists. (i.e. known tracking companies)

          This just expanded that original functionality, by making it happen on any domain, and have it be the default for all users, rather than an opt-in feature of Enhanced Tracking Protection.

          • ripcord@lemmy.world
            link
            fedilink
            English
            arrow-up
            8
            ·
            edit-2
            22 days ago

            That’s not what I was thinking of, which was even more fundamental. But that’s good info (and another way to cover stuff in the article).

            Edit: what I was thinking originally was really stupid, that 3rd-party cookies weren’t allowed at all. Which was really dumb since of course they are.

        • Telorand@reddthat.com
          link
          fedilink
          English
          arrow-up
          24
          ·
          22 days ago

          They’ve been doing this with container tabs, so this must be the successor to that idea (I’m going to assume they’ll still have container tabs).

          • jollyrogue
            link
            fedilink
            English
            arrow-up
            19
            ·
            21 days ago

            Container tabs are still a thing in FF. This is based on that work, if I remember correctly.

              • Kushan@lemmy.world
                link
                fedilink
                English
                arrow-up
                5
                ·
                21 days ago

                Same, they’re an absolute game changer for me. I have to use multiple different identities in work due to separate active directories and container tabs makes it super easy

          • snaggen@programming.dev
            link
            fedilink
            English
            arrow-up
            7
            ·
            21 days ago

            Container tabs are still useful, as they let you use multiple Cookie jars for the same site. So, it is very easy to have multiple accounts on s site.

      • Buddahriffic@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        21 days ago

        From my experience, blocking 3rd party cookies in general doesn’t seem to make any difference for site functionality anyways. Though I never log into sites with a Google or FB account other than Google or FB sites (and rarely at all for the latter).

    • Liam Mayfair@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      6
      ·
      22 days ago

      Isn’t this basically Firefox’s version of the third party cookie block that Chrome rolled out a few months ago? Or am I missing something here?

      I mean, it’s good news either way but I just want to know if this is somehow different or better.

      • jollyrogue
        link
        fedilink
        English
        arrow-up
        10
        ·
        21 days ago

        Sites are much more contained now. Is much more like a profile per site.

      • The Quuuuuill@slrpnk.net
        link
        fedilink
        English
        arrow-up
        10
        ·
        22 days ago

        It increases implementation complexity of the browser and loses people who fund Firefox and contribute code $$$