4 ms·
> every website gets to read only its own cookies That's already the case, isn't it? It's just that embedded parts by a 3rd party can set their own cookies, wh
by red_trumpet 4y ago
> every website gets to read only its own cookies
That's already the case, isn't it? It's just that embedded parts by a 3rd party can set their own cookies, which can be read by the 3rd party whenever it is embedded in any other page.
- aidenn0 4y agoIt's not already the case, but it is expected to be the case in all major browsers sometime next-year[1] 1: https://en.wikipedia.org/wiki/HTTP_cookie#Third-party_cookie https://en.wikipedia.org/wiki/HTTP_cookie#Third-party_cookie
- cortesoft 4y agoYou aren’t disagreeing with the person you are responding to, you just have slightly different ideas what it means when someone says “website” You are calling all of the assets loaded, no matter from where, as one “website”. The person you are replying to considers each domain for each asset on the single page as being different “websites”
- TylerE 4y agoThen they should say server/domain/subdomain and not “website”.