• ArchRecord@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months 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
      0
      ·
      3 months 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
        0
        ·
        edit-2
        3 months 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.

        • Telorand@reddthat.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months 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).