As AlienBOB points out in the article below, you merely need to set GOOGLE_API_KEY, GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET variables in your .profile or .bash_profile and you're good to go with their public key.

No biggy, and you can still use your 32 bit Chromium packages just like before (there's a lot of people running 32 bit systems still)




Also this, by him, in that same thread:

If someone starts a project to create a truly open Sync server for Chromium then I would consider packaging it for Slackware of course. The Brave project has built a Sync server for their Chromium-based Brave browser: github.com/brave/go-sync


But like Mozilla's original Weave sync server, I would like for a Chromium Sync server to be written in such a way that it can be self-hosted. I only trust myself.

· · Web · 0 · 2 · 1
Sign in to participate in the conversation
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko