Chronotope’s avatarChronotope’s Twitter Archive—№ 154,145

        1. My concerns with Topics API have little to do with its technical approach and everything to do with the wide scummy world of ad tech intermediaries and the ecosystem in which they might use Topics API perhaps for the better, but I fear for worse. aramzs.github.io/web-standards/2022/08/04/topics-api-review.html
          OpenGraph image for aramzs.github.io/web-standards/2022/08/04/topics-api-review.html
          Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets ❤️ 9 Favorites Mood -3 🙁
      1. …in reply to @Chronotope
        After Ryanbarwick's excellent article talking about Topics API I thought it might be nice to add additional detail around my specific concerns to the conversation marketingbrew.com/stories/2022/07/28/publishers-are-concerned-google-s-topics-will-lead-to-a-higher-ad-tech-tax
        OpenGraph image for marketingbrew.com/stories/2022/07/28/publishers-are-concerned-google-s-topics-will-lead-to-a-higher-ad-tech-tax
        Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood +6 🙂
    1. …in reply to @Chronotope
      I come here not to bury Topics API, I have high hopes for browser mediation of ad systems as a strategy to exit the world of third party cookies. I hope that we might see Topics API develop into a more effective product that can improve the ad tech ecosystem.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 3 Favorites Mood +8 🙂
  1. …in reply to @Chronotope
    Hopefully my feedback can be useful here.
    On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood +4 🙂

Search tweets' text