Michael Kleber

I tried to address this question in the very next bullet point: > * The intent is to let the first party retain control over identity on their site. A...

My goal of that section was challenging precisely the part that confused you! Script running on page can get access to any state stored in JS, which is why I...

I agree that the web should support ways to accomplish all of these! Regarding logins, for example, something like https://github.com/mikewest/http-state-tokens by @mikewest is a path forward; there are a very...

We're agreed that "a publisher's ability to monetize content is a necessary component". I don't personally know of a way other than programmatic advertising to support a web anything like...

Hooray, this is great: > we should establish for example what identity principles are in the interest of users and match user expectations, then figure out what those principles would...

> So are you saying that the identity principles that you are basing your work on is only that "nobody off the browser can reconstruct the user's multi-site browsing history"?...

Excellent question! And I think one that needs to be answered as part of the discussion with the ads industry as well as the web development community. But this work...

Quoting myself from https://github.com/michaelkleber/turtledove#pigin :-) : > Feedback from the W3C Web-Advertising Business Group and Privacy Interest Group and from the browser and privacy research communities highlighted weaknesses in that...

I was hoping this was addressed by the bullet > The notion of "First Party" may expand beyond eTLD+1, e.g. as proposed in [First Party Sets](https://mikewest.github.io/first-party-sets/). Was the Mozilla policy's...

Thank you very much for pointing this out! Apologies that I wasn't aware of this very important subtlety. Do you feel that enforcing that distinction is technically feasible? The embedded...