4 ms·

Worked for years. Even showed up in the GCP dashboard as having access. Had no idea it “private”. We just plugged in credentials from Google as per chromium bui

by suhail 6y ago

Worked for years. Even showed up in the GCP dashboard as having access. Had no idea it “private”. We just plugged in credentials from Google as per chromium build instructions. They knew we and others were using it because there are stats. Now we are given 2 months to develop a completely new solution.

lima 6y ago
The Chromium build instructions are very clear on this: https://www.chromium.org/developers/how-tos/api-keys https://www.chromium.org/developers/how-tos/api-keys > Note that the keys you have now acquired are not for distribution purposes and must not be shared with other users. > Many of the Google APIs used by Chromium code are specific to Google Chrome and not intended for use in derived products. In the API Console (http://developers.google.com/console http://developers.google.com/console) you may be able to purchase additional quota for some of the APIs listed above. For APIs that do not have a "Pricing" link, additional quota is not available for purchase. The notice has been there since 2013, when the page was first archived: https://web.archive.org/web/20131211101458/https://www.chromium.org/developers/how-tos/api-keys https://web.archive.org/web/20131211101458/https://www.chrom...
- deleted 6y ago
  [deleted]
- suhail 6y ago
  Buried in depths of their documentation? It’s also worked for years too. Google has docs that are completely outdated and neglected. Chrome Extension docs didn’t get updated for 5+ years until recently. Why put it in the console then? Why have tool tips that say “Access to this API is enabled.” There’s no improvement to security. This will be a cake walk to reverse engineer. I don’t see how my point is invalid.
  - lima 6y ago
    > Buried in depths of their documentation? You mean right in the instructions on how to acquire them? > It’s also worked for years too. It was tolerated for years, but it was always on very shaky ground. Now Google pulled the rug. I'm annoyed because that means my Chromium AUR package stops working, and I'll have to pry the tokens from a release build, but this isn't unexpected. > Why put it in the console then? Why have tool tips that say “Access to this API is enabled.” For outside developers who want to work on Chromium. This is also CLEARLY stated in their docs. > There’s no improvement to security. This will be a cake walk to reverse engineer. They didn't say it was about security.

by suhail 6y ago

lima 6y ago

The Chromium build instructions are very clear on this: https://www.chromium.org/developers/how-tos/api-keys https://www.chromium.org/developers/how-tos/api-keys > Note that the keys you have now acquired are not for distribution purposes and must not be shared with other users. > Many of the Google APIs used by Chromium code are specific to Google Chrome and not intended for use in derived products. In the API Console (http://developers.google.com/console http://developers.google.com/console) you may be able to purchase additional quota for some of the APIs listed above. For APIs that do not have a "Pricing" link, additional quota is not available for purchase. The notice has been there since 2013, when the page was first archived: https://web.archive.org/web/20131211101458/https://www.chromium.org/developers/how-tos/api-keys https://web.archive.org/web/20131211101458/https://www.chrom...

deleted 6y ago
[deleted]
suhail 6y ago
Buried in depths of their documentation? It’s also worked for years too. Google has docs that are completely outdated and neglected. Chrome Extension docs didn’t get updated for 5+ years until recently. Why put it in the console then? Why have tool tips that say “Access to this API is enabled.” There’s no improvement to security. This will be a cake walk to reverse engineer. I don’t see how my point is invalid.
- lima 6y ago
  > Buried in depths of their documentation? You mean right in the instructions on how to acquire them? > It’s also worked for years too. It was tolerated for years, but it was always on very shaky ground. Now Google pulled the rug. I'm annoyed because that means my Chromium AUR package stops working, and I'll have to pry the tokens from a release build, but this isn't unexpected. > Why put it in the console then? Why have tool tips that say “Access to this API is enabled.” For outside developers who want to work on Chromium. This is also CLEARLY stated in their docs. > There’s no improvement to security. This will be a cake walk to reverse engineer. They didn't say it was about security.