• kobra@lemm.ee
    link
    fedilink
    arrow-up
    60
    ·
    11 hours ago

    Makes sense. It was an idealistic idea that was never going to work because it would rely on advertisers honoring a consumer’s request.

  • kbal@fedia.io
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    7 hours ago

    While the feature itself was not so useful, I do worry slightly about what the motivation for its removal might’ve been. People suggest that it’s to avoid literally 1 bit of fingerprint data but the lack of more significant action on that front seems to contradict that idea. I didn’t find any discussion of it in bugzilla, which used to be where you’d go to find out what the hell they’re thinking.

    Did they think nobody would notice? Are they going back to the bad old habit of removing features just for the sake of removing features? Did the fact that so many of their users have that flag set interfere with their ad tracking ambitions?

    • ProtonBadger@lemmy.ca
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      4 hours ago

      Did they think nobody would notice?

      Very unlikely, they’re doing it openly and they know from experience that all changes are always immediately reported in the community. They operate this way by choice.

      Are they going back to the bad old habit of removing features just for the sake of removing features?

      Doubt it, DNT is not only useless it is misleading as the user may think it is effective while in reality it allows “better” fingerprinting.

      Did the fact that so many of their users have that flag set interfere with their ad tracking ambitions?

      Source? I thought reports had usually been that it saw extremely low adoption on the client but maybe I’m wrong. Best rates I could find was <9% on desktop and 19% on mobile but that’s back when it was most talked about.

      • kbal@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        2 hours ago

        If “do not track” was already in use by 10-20% of Firefox users a year after it became available, at a guess I’d say maybe it got to at least 20-30% over time, considering how popular the idea became in the years following that. But let me know if you find actual data I guess, that might be interesting.

        At any rate, having to refrain from tracking ad attribution by default for even just 10% of users would be a substantial cost in the future where that system becomes a big source of revenue.

        I’m not saying that’s their motivation, just that it seems roughly plausible that it might be, in the absence of a better explanation.

  • Zagorath@aussie.zone
    link
    fedilink
    arrow-up
    17
    ·
    10 hours ago

    Without the force of law, this was never going to work.

    Perhaps if the EU had used the presence of absence of the Do Not Track header as their method of determining cookie consent, it could have ended up being useful both from a privacy standpoint and to have saved us from the scourge of annoying as fuck cookie banners they ended up causing. Ah well.

  • JasminIstMuede@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    24
    ·
    11 hours ago

    Unfortunate, but understandable :(
    I wish we could rely on good faith with something like this, but it seems the only way is to block as much tracking as possible by force.