|
|
|
|
|
by peey
2025 days ago
|
|
AOSP is an open source project, which is impractical for any business to run because of apps' reliance on proprietary google play services. Chromium is an open source project, but proprietary chrome has the largest browser market share and they like to abuse their position to not play well with standards bodies. Google can develop Fuchsia. It'll even be cool piece of tech, but I do not for a second believe that contributing to the project would benefit anyone but Google. |
|
If built without API keys, Chromium warns 'Google API keys are missing. Some functionality of Google Chrome will be disabled.' [4] [5]
The APIs used include [6]:
* Calendar API
* Contacts API
* Drive API (Optional)
* Chrome Remote Desktop API
* Chrome Spelling API
* Chrome Suggest API
* Chrome Sync API
* Chrome Translate Element
* Chrome Web Store API
* Chrome OS Hardware ID API (Optional, Chrome OS)
* Device Registration API (Optional, Chrome OS)
* Google Cloud DNS API
* Google Cloud Storage
* Google Cloud Storage JSON API
* Google Maps Geolocation API (Optional)
* Google Maps Time Zone API
* Google Now For Chrome API (Optional)
* Nearby Messages API
* Safe Browsing API
* Speech API
[1] https://git.alpinelinux.org/aports/tree/community/chromium/A...
[2] https://github.com/archlinux/svntogit-packages/blob/packages...
[3] https://git.launchpad.net/~chromium-team/chromium-browser/+g...
[4] https://chromium.googlesource.com/chromium/src/+/9a11dadde80...
[5] https://sources.debian.org/patches/chromium/83.0.4103.116-1~...
[6] https://www.chromium.org/developers/how-tos/api-keys