Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why mandate that geo hint is tied to an IP geolocation feed? #194

Open
npdoty opened this issue Apr 27, 2022 · 0 comments
Open

why mandate that geo hint is tied to an IP geolocation feed? #194

npdoty opened this issue Apr 27, 2022 · 0 comments
Labels

Comments

@npdoty
Copy link

npdoty commented Apr 27, 2022

If this is an optional and user-controlled geolocation hint, then I would expect that some clients would have access to course geolocation but not necessarily have an IP-geolocation database that they want to look up. Is it necessary to prohibit clients from taking what they know to be current approximate geolocation and adding it as a client hint?

Similarly, do we want the header name to include IP? We might move to IP address not being a good proxy for geolocation (indeed, this seems like part of that project), and it seems like the use cases are for the client to indicate course geolocation, not actually to indicate anything related to the Internet Protocol for more than historical reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants