• ripcord@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    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 making them world-readable for tracking, and this breaks that.

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

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