I think you misunderstand the use case, because neither example makes sense for this proposal. Try this: A podcast listening app. It reads RSS and caches audio files for use offline. Today all that routes through the app's server, even though it's handling public resources.
We operate such a service today. Idea is we resolve these request's host *only* via that path, and cert must line up with resolved IP.
Can make it configurable as a (new) group policy (and disableable) for the paranoid.
I'm sure there's a hole in this... 


-
-
are you proposing leaking hostnames to Google independent of normal OS DNS settings?
-
Or whomever else you set as your "public only" resolver, yes. If the issue is DNS being overloaded for public/private (and another decade+ of this debate about something *every native app can do*), let's disentangle DNS.
- 7 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
