If I'm reading this right, it means the custom Chromium build I use[0] won't work like I want it to anymore. Although not required if you want to be "ungoogled" which many here do, I personally set up all the required API keys against my personal account as per their guide[1] so that Chromium works like Google Chrome as much as possible, since that's the browser I otherwise use. The issue is that now I can't have hardware-accelerated graphics on Chrome on Linux (since they refuse to put that in their mainline build[2]) and have it be synced in the same way as the official browser, since they're removing syncing from Chromium.
After reading the email[3] they sent out to Slackware devs, it's not clear if they are just removing this ability for builds that have keys built in, or if they are completely removing the ability to add your own keys to Chromium like I have in my example above. Could someone help clarify this?
After reading the email[3] they sent out to Slackware devs, it's not clear if they are just removing this ability for builds that have keys built in, or if they are completely removing the ability to add your own keys to Chromium like I have in my example above. Could someone help clarify this?
[0] https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-...
[1] https://www.chromium.org/developers/how-tos/api-keys
[2] https://bugs.chromium.org/p/chromium/issues/detail?id=463440
[3] https://groups.google.com/a/chromium.org/g/embedder-dev/c/NX...