go-sync

FWIW, the thread at https://groups.google.com/a/chromium.org/g/embedder-dev/c/NX... says: > The Brave project has built a Sync server for their Chromium-based Brave browser: https://github.com/brave/go-sync and it is open source but uses Amazon Cloud for their database backend storage.

I think what you're describing are the "Tip" buttons which can be added on a few supported sites (which can be disabled). They aren't selling anything- it's a feature which people can use if they like. The server implementation for sync is mostly compatible with Chromium and can be used without Brave. Someone could clone https://github.com/brave/go-sync and stand up their own server. It would require some patches on top of Chromium (similar to what is done in Brave) to implement the authentication - but once that is done, all of the Chromium tools like chrome://sync-internals work just fine

The service itself is open source and can be hosted by a community. It has a different authentication scheme (ex: not Google accounts) and enforces client side encryption by default. See https://github.com/brave/go-sync for more information The official service hosted by Brave is only intended to be used with Brave Browser

It would take require changes to Chromium (with regards to authentication), but Brave's sync server is open source and protocol-wise mostly compatible (client side encryption is enforced): https://github.com/brave/go-sync I doubt Chromium authors would accept changes to authentication (even if you put guards around it like `#ifndef GOOGLE_CHROME_BRANDING`). If there were a 100% compatible service available, you can change the service URL using CLI arg `--sync-url` There is also a local sync backend which is interesting as it writes to disk. You could potentially sync this via OneDrive or something similar. You can enable with the CLI arg `--enable-local-sync-backend`. Directory settable using `--local-sync-backend-dir` You can watch the data being synced via chrome://sync-internals