← Back to context

Comment by kps

5 years ago

> the public suffix list is (sadly) how you communicate that to browsers

Sadly, indeed. Had they never heard of DNS?

6 comments

kps

Reply
jefftk  5 years ago

How would you propose handling this with DNS? Here are some things it covers:

* a.example.com and b.example.com are the same site

* a.co.uk and b.co.uk are not the same site

* a.cloudfront.net and b.cloudfront.net are not the same site

* a.higashikawa.hokkaido.jp and b.higashikawa.hokkaido.jp are not the same site

* a.example.higashikawa.hokkaido.jp and b.example.higashikawa.hokkaido.jp are the same site

There is a proposal to do something similar using response headers and .well-known urls: https://github.com/privacycg/first-party-sets

  • folmar  5 years ago 

      _i_am_tld.cloudfront.net IN TXT "yes"
  _i_am_tld.higashikawa.hokkaido.jp IN TXT "yes"

    • jefftk  5 years ago

      This requires sites to opt in before it works, right? I think this would have been hard to introduce, because it requires so much coordination.

      2 replies →