• smeg@feddit.uk
      link
      fedilink
      English
      arrow-up
      41
      ·
      12 days ago

      That is exactly the reason for this change. It often didn’t work and probably makes you easier to fingerprint.

        • smeg@feddit.uk
          link
          fedilink
          English
          arrow-up
          11
          ·
          12 days ago

          This option is built on top of the Global Privacy Control (GPC). GPC is respected by increasing numbers of sites and enforced with legislation in some regions.

          Sounds like Mozilla at least think it’s better

    • Don_alForno@feddit.org
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      9
      ·
      12 days ago

      That doesn’t absolve them.

      With the feature removed, websites can act like they didn’t even go against my wishes.

  • maniacalmanicmania@aussie.zone
    link
    fedilink
    English
    arrow-up
    27
    ·
    edit-2
    12 days ago

    However, as we approach 2025, with growing concerns about online privacy and data protection, Mozilla believes that DNT is no longer an effective privacy measure. Many websites ignore the DNT signal. Therefore, Mozilla has removed the DNT signal from Firefox version 135.

    Mozilla believes that privacy preference is not honored by websites and that sending the Do Not Track signal may impact your privacy. The company has updated Firefox’s Do Not Track help support page to confirm that.

    The company recommends using the Global Privacy Control setting as an alternative to prevent websites from tracking user data.

    • LWD@lemm.ee
      link
      fedilink
      English
      arrow-up
      15
      ·
      edit-2
      12 days ago

      I think the article made a typo that claims GPC is the same as DNT.

      When you enable the feature, the GPC sends a signal… This signal is sent via a special HTTP header called DNT: 1 (Do Not Track)

      But the GPC spec does say it sends a new signal: Another header (like DNT) and a JavaScript variable the client would set. I don’t see why this couldn’t be used for tracking too.

      A user agent MUST generate a Sec-GPC header

      So if it generates a header, it can still be used for fingerprinting, but this header is actually less restrictive for what the receiver must do.

      DNT was “do not track,” and GPC is "do not sell:

      GPC is also not intended to limit a first party’s use of personal information within the first-party context (such as a publisher targeting ads to a user on its website based on that user’s previous activity on that same site).

  • Lumidaub@feddit.org
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    2
    ·
    12 days ago

    If you wish to ask websites to respect your privacy, you can use the “Tell websites not to sell or share my data” setting. This option is built on top of the Global Privacy Control (GPC). GPC is respected by increasing numbers of sites and enforced with legislation in some regions.

    So is the difference that DNT was asking for no tracking at all while this GPC setting allows for tracking data to be created but not forwarded to third parties? That seems reasonable, not all “tracking” is malicious. Though I wonder why, if DNT isn’t respected, any other vaguely similar setting would be.