Problem with this is that it needs the sync server:
> Since the Mozilla-hosted sync servers will not trust assertions issued by third-party accounts servers, you will also need to run your own sync-1.5 server.
This is the issue to watch, supporting SQLite. This makes it feasible to run a simple sync server for a single user or a small group. But this is not moving forward.
This article is from 2018, and contains a single update from 2020. I would think the terrain has shifted in the last 3 years, so take the article with an appropriate pinch of salt.
Isn't it somewhat hilarious that the author of Adblock Plus, far and away the largest privacy risk faced by anyone, throws this much shade on Google's privacy protections? ABP gets unfettered, full and complete access to all your data no matter how sensitive and only the publisher's OpSec stands between the user and total exposure.
> Update (2020-06-10): The issue has been resolved in Chrome 80. The key derivation algorithm used now is scrypt with N=8192, r=8, p=11. These values are sane and should make attacks against most passwords unrealistic.
Yes, they fixed this particular issue (and a few more), the article mentions it. But the update I published today explains why Chrome Sync is still very bad privacy-wise (as opposed to outright horrible which it was back in 2018). https://palant.info/2023/08/29/chrome-sync-privacy-is-still-...
Readit News
> Since the Mozilla-hosted sync servers will not trust assertions issued by third-party accounts servers, you will also need to run your own sync-1.5 server.
The tutorial refers to the old unmaintained version: https://github.com/mozilla-services/syncserver, see https://github.com/mozilla-services/syncserver/commit/8d9804...
The alternative is https://github.com/mozilla-services/syncstorage-rs which is ridiculously hard to set up.
> https://github.com/mozilla-services/syncserver/pull/294
> So basically they stopped running the older version themselves but don't consider the newer version production-ready yet. What a mess.
This doesn't seem to have improved much since...
Some of my experience self-hosting the whole stack previously:
https://news.ycombinator.com/item?id=30315816
https://news.ycombinator.com/item?id=30727935
[0]: https://news.ycombinator.com/item?id=30728966
https://github.com/mozilla-services/syncstorage-rs/issues/49...
This is the issue to watch, supporting SQLite. This makes it feasible to run a simple sync server for a single user or a small group. But this is not moving forward.
Floccus for bookmarks (https://floccus.org/) : it works also on mobile devices : a great plus ! You need only a webdav server (or a Nextcloud account), I use Dave (https://github.com/micromata/dave)
Vaultwarden for the passwords (https://github.com/dani-garcia/vaultwarden)
A huge advantage of this solution is that you can have synchronization also between different browsers and on mobile devices.
Yes, they fixed this particular issue (and a few more), the article mentions it. But the update I published today explains why Chrome Sync is still very bad privacy-wise (as opposed to outright horrible which it was back in 2018). https://palant.info/2023/08/29/chrome-sync-privacy-is-still-...
Google moderates Google Collections items - https://news.ycombinator.com/item?id=37301600 - Aug 2023 (38 comments)