Chronotope’s avatarChronotope’s Twitter Archive—№ 132,694

                      1. UUID schemes like UID2 are inherently incompatible with literally all of the post-cookie browser proposals. This does not bode well for their future.
                        Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 5 Retweets ❤️ 19 Favorites Mood +2 🙂
                    1. …in reply to @Chronotope
                      Chrome monitors ad-related traffic in-browser and is therefore prepared to intervene against specific requests and styles of requests - chromium.googlesource.com/chromium/src/+/master/docs/ad_tagging.md
                      OpenGraph image for chromium.googlesource.com/chromium/src/+/master/docs/ad_tagging.md
                      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 4 Favorites Mood +1 🙂
                  1. …in reply to @Chronotope
                    Webkit has outright declared that they will not be allowing simultaneous use of new (soon to be the only way) to do conversion tracking AND UUID schemes Chronotope/1359915691516841985
                    Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 6 Favorites Mood 0
                1. …in reply to @Chronotope
                  Firefox's existing interventions and partnership with the Disconnect list mean that there is no way UUID requests are flowing through that browser.
                  Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 3 Favorites Mood -1 🙁
              1. …in reply to @Chronotope
                Microsoft Edge's proposal notes the need to split requests that include identifying data from any new methodology - github.com/WICG/privacy-preserving-ads/blob/main/Parakeet.md
                OpenGraph image for github.com/WICG/privacy-preserving-ads/blob/main/Parakeet.mdoh my god twitter doesn’t include alt text from images in their API
                Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 3 Favorites Mood 0
            1. …in reply to @Chronotope
              Something like FLoC or Turtledove is on-its-face incompatible with UUIDs as they turn FLoC IDs into tracking vectors instead of anonymizing ones.
              Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 5 Favorites Mood +2 🙂
          1. …in reply to @Chronotope
            Advertisers are going to have to choose, do they want data-rich contextual, cross-site contextual, & conversion tracking.... or pointlessly attempting to challenge tech in an arms race over tracking individuals--a thing not possible in any other ad medium. Chronotope/1369296644198502401
            Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 9 Favorites Mood 0
        1. …in reply to @Chronotope
          So much effort, time and money going into a thing that isn't needed and isn't possible to preserve as a technique past--at best--the next few years. Chronotope/1381951319615938563
          Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 6 Favorites Mood 0
      1. …in reply to @Chronotope
        That the conversation has even moved so far in the direction of 1 to 1 user tracking at a time when literally everyone outside of the ad tech industry is calling for *less* tracking of individuals is insane & challenges the idea most ad tech serves advertiser, user or publisher.
        Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets ❤️ 4 Favorites Mood -2 🙁
    1. …in reply to @Chronotope
      Unique User Identification for web advertising is an already rotting branch of technological development. Step on to it with caution and the knowledge that if it supports you at all, it won't for long. This is where many have to be right now, but it won't last.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 7 Favorites Mood +2 🙂
  1. …in reply to @Chronotope
    1-to-1 cross-site individualized user tracking ain't it chief
    On twitter.com Twitter logo Chronotope’s avatar ❤️ 4 Favorites Mood 0

Search tweets' text