Chrome's geolocation fails daily due to API limit

Re:Chrome's geolocation fails daily due to API limit by gondo on Wednesday August 09, 2017 @01:13AM (#14965723)

i don't understand what do you mean. how can i do that? f.e. how would i do that with AWS API?

the thing with chromium is: it is open source (you can find the credentials), it is meant to be used on any computer via any IP (you can't whitelist API requests)

[ Parent | on HN ]

Re:Chrome's geolocation fails daily due to API limit by ktta on Wednesday August 09, 2017 @02:24AM (#14966026)

>the thing with chromium is: it is open source (you can find the credentials)

No, you have to get your own API keys via Google Cloud API Manager before building chromium. That's the reason why Chromium on Windows doesn't let you log in.

I presume Chromium on linux distros will use an API key of the package maintainer.

Also, in most closed source binaries (which chrome is a part because it has binary blobs not present in Chromium - see Google Cast, etc) you will have to sign a EULA where you agree to no disassemble and use that API key, so doing so is illegal too.

[ Parent | on HN ]

Re:Chrome's geolocation fails daily due to API limit by Gaelan on Wednesday August 09, 2017 @02:24AM (#14966028)

Chromium != chrome. It doesn’t add much security, but I bet the API keys are added as part of whatever process google uses to build chrome from the chromium source

[ Parent | on HN ]