Chronotope’s avatarChronotope’s Twitter Archive—№ 115,570

    1. Enjoying aripap on adexchanger.com/podcast/the-big-story/the-big-story-chromes-cookie-carnage/ he's right, for the question of who can comment and contribute: the answer is anyone. I highly encourage you to poll your vendors, explain to them what is going on if they don't know, and parse their concerns and take some to the repos.
      OpenGraph image for adexchanger.com/podcast/the-big-story/the-big-story-chromes-cookie-carnage/
      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets ❤️ 6 Favorites Mood +4 🙂
  1. …in reply to @Chronotope
    aripap I don't think *every* concern an ad tech vendor you use is going to be something you, a publisher engineer, is worried about. There will likely be defensiveness & overreactions. But, the flip side of this is that, as people working on the TLD, no one is better situated to assess.
    On twitter.com Twitter logo Chronotope’s avatar Mood -2 🙁
    1. …in reply to @Chronotope
      aripap It's no secret that I'm not a fan of the majority of ad tech, but we do work with some partners for a reason, and if that reason is counteracted by upcoming changes you have to ask: Is this change going to hurt just the vendor or both of us?
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood 0
      1. …in reply to @Chronotope
        aripap The answers will differ depending on the issue and the vendor, but some *will* likely align. If that's the case, then you have to ask if a universal change that both of you find threatening would still be a threat if it was applied universally to the web. Like...
        Permalink On twitter.com Twitter logo Chronotope’s avatar Mood -2 🙁
        1. …in reply to @Chronotope
          aripap User-based targeting going away sounds like something that threatens us all, but only because we live in a world where it is an option. If no one had that option, it would re-balance the playing field for the better. Not a threat to a TLD/publisher (tho prob to many vendors).
          Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets ❤️ 4 Favorites Mood -1 🙁
          1. …in reply to @Chronotope
            aripap But there are parts of the industry like ad fraud prevention that are full-ad-tech-stack concerns, right up to the TLD. If your vendor can articulate their use case for a vanishing technology and it qualifies for your concern, taking it to a GitHub issue is the way to go!
            Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 3 Favorites Mood -2 🙁
            1. …in reply to @Chronotope
              aripap And the main thing to remember is: this isn't an attack, a better and more private web is a promise of a better web for TLDs/Publishers too.
              Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +4 🙂
              1. …in reply to @Chronotope
                So my advice is take your concerns and make a question out of it: it isn't OMG This is Going Away. It's: how can we take this functionality and still support it while respecting user privacy?
                Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood +2 🙂
                1. …in reply to @Chronotope
                  And are you curious about how you can model and explain your use case? Well, we've got examples for that! github.com/w3c/web-advertising
                  OpenGraph image for github.com/w3c/web-advertising
                  Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets Mood +1 🙂
                  1. …in reply to @Chronotope
                    It is easy to lose track of the idea the web should be built in the open, especially when it feels like a lot is being developed behind closed doors. But, a lot of it is still happening open-source. Incentivize the browsers to continue doing so by contributing...
                    Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood +3 🙂
                    1. …in reply to @Chronotope
                      Here are a list of Privacy Sandbox project GitHubs you can contribute to: chromium.org/Home/chromium-privacy/privacy-sandbox
                      OpenGraph image for chromium.org/Home/chromium-privacy/privacy-sandbox
                      Permalink On twitter.com Twitter logo Chronotope’s avatar Mood 0
                      1. …in reply to @Chronotope
                        Now, I'm all for loudly complaining if you make your case and you think it is reasonable and it gets ignored. Be vocal, be angry, and be angry on behalf of your users too, who don't want to be tracked and bombarded with shitty ads. But you gotta at least state your case first.
                        Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood -14 🙁
                        1. …in reply to @Chronotope
                          Now who knows, perhaps everything we have to say and propose will get ignored (be it pro-privacy or pro-ads) and we end up in a real shitty situation. If so I'll be here on Twitter with the flame gifs on. But, if you don't at least try, it gives an excuse to be less open-source.
                          Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood -6 🙁
                          1. …in reply to @Chronotope
                            And the next round will then only feel worse. :/
                            Permalink On twitter.com Twitter logo Chronotope’s avatar Mood -3 🙁
                            1. …in reply to @Chronotope
                              Our goal should be a privacy-first web, but also a free and open internet. And a good way to keep the free part is with privacy-respecting advertising and a great path towards that is removing the opportunity for bad ad tech to work. Don't protect the status quo, we NEED change.
                              Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 5 Favorites Mood +6 🙂

Search tweets' text