๐ PSA: You can enable the revoked Google features on Chromium by using your personally enrolled API keys
๐ก Newskategorie: Linux Tipps
๐ Quelle: reddit.com
For those who just loves Chromium for whatever reason (me being to use chromium-freeworld
for the codecs and hardware-accelerated video playback) and (want/used) to use their revoked Google features, you can legitimately re-enable those features by rolling your own API key on Google Cloud Platform.
Google Sync on Chromium (Freeworld) 89
Instructions are shown here (chromium.org), but I'll show them here because some of the steps are pretty inaccurate and outdated
Instructions:
Acquiring the API access
- Subscribe to the [[email protected]](mailto:[email protected]) mailing list to gain access to the relevant APIs needed
- Go to https://cloud.google.com/console and create a new project under a Google account with the email registered to the mailing list subscription
- Open "APIs & Services" > "Library" in the sidebar and enable the following APIs
- Admin SDK API
- Chrome Sync API
- Geolocation API
- Cloud Search API
- Time Zone API
- Safe Browsing API
- Go to the "Credentials" page under APIs & Services
- Click "Create credentials" and then select "OAuth client ID" from the list
- You may be required to do "Configure consent screen", do it and fill the details freely, after that, you will have to go create an OAuth client ID again
- Select "Desktop app" as the Application type
- Pick a name of your liking -- it can be anything
- Create the client ID
- You'll see a "client ID" and "client secret". Keep them in a text file (or write it down), then dismiss the dialog box
- Click "Create credentials" and then select "API key" from the list
- A dialog box will show the API key, save it too
- Basically, you're done. You can now use it
(Re)enabling the features
Basically you have 2 ways to reenable them, first, you can provide the keys at compile time so that it'll be one with the binary, or you can just provide them at runtime, which is the easier to be done by most people.
Build chromium with the keys
To do so, you must specify these variables in the args.gn file:
google_api_key = "yourAPIKey" google_default_client_id = "your.client.id" google_default_client_secret = "yourClientSecret"
And then build chromium
Run chromium with the keys
To do so, you can just run: env GOOGLE_API_KEY='yourAPIKey' GOOGLE_DEFAULT_CLIENT_ID='your.client.id' GOOGLE_DEFAULT_CLIENT_SECRET='yourClientSecret' chromium
And to configure it to automatically use the keys there are 3 ways:
- Modify
~/.bashrc
or/etc/environ
(to apply globally) and add the environment variables - Modify the .desktop file to run the
env
command - Create a wrapper shell script
And that's it! That way you can get any build of chromium (except ungoogled) to have the "missing" features back
Hope this helps
[link] [comments] ...