3 ms·

Abuse is subjective. Outside of Google, the general sentiment is that Chrome treating doubleclick.com as a first party to anything other than doubleclick.com is

• Wowfunhappy 3y ago
  Couldn't Google easily achieve the same by just moving their ads to doubleclick.google.com?
  • kokanee 3y ago
    That would allow them to share doubleclick cookies across all subdomains of google.com. This FPS feature will allow them to share doubleclick cookies (or whichever cookies) across any domains that they choose to group into a "set." So regardless of whether you selected the "block third party cookies" setting, Chrome now ships with an internal list of domain groups for which it will ignore that setting.
    • deleted 3y ago
      [deleted]
    • joshuamorton 3y ago
      Right as the parent mentions, it only allows grouping among sites that are logically owned by the same entity anyway, if someone wanted to make this work with first-party cookies, they could redirect from myapplication.com to myapplication.owning-party.com (which is what google does with gmail.com -> mail.google.com today) This just allows you to do that while maintaining security boundaries around things like user generated content (e.g. facebook.com vs. fbcdn.net). This doesn't allow some random site that uses third party ads to allow doubleclick cookie access, or vice versa.
      • Wowfunhappy 3y ago
        ^ This was my understanding too, so if it's wrong I'd like to know why! (The parent post is downvoted as of this posting.)