Chronotope’s avatarChronotope’s Twitter Archive—№ 151,380

        1. While Topics API is an improvement over FLoC, it's hardly a perfect solution and there's clearly a lot of conflict over if it works and exactly who it advantages. The 1 new topic/week specified in Google's blog post seems not useful for 1 domain pubs - adweek.com/programmatic/googles-privacy-sandbox-origin-trials/
          OpenGraph image for adweek.com/programmatic/googles-privacy-sandbox-origin-trials/
          Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 5 Retweets ❤️ 29 Favorites Mood +5 🙂
      1. …in reply to @Chronotope
        My hope is that we'll see the Chrome team move forward on ways to give different pages under a domain different topics, but my concern is that the privacy guarantees seem to be tied to the one-calculation-per-domain setup.
        Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 4 Favorites Mood +2 🙂
    1. …in reply to @Chronotope
      However, as long as the topics are limited per-domain, I really worry about how it enables and supports particular sketchy multi-domain-network business models if it were to go live.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 2 Favorites Mood -2 🙁
  1. …in reply to @Chronotope
    Some interesting alternatives to differentiate on: - lowest level directory - Schema dot org genre or author - OpenGraph article:section - Some other metadata structure that might be commonly used but I don't know about?
    On twitter.com Twitter logo Chronotope’s avatar ❤️ 3 Favorites Mood +1 🙂
    1. …in reply to @Chronotope
      But yeah... in many ways I feel like we can't even really think about how Topics could work for us until it does more than terms per top level domain.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood +5 🙂

Search tweets' text