News for hackers. Stuff that matters.
Re:Private by Design: How We Built Firefox Sync by colemickens on Tuesday November 13, 2018 @11:42PM (#18447554)
Aren't both Chrome and Firefox's sync protocols open? At least, the Firefox Sync server is still self-hostable and open source, and at least the client side of Chrome's sync is open source since Chromium can sync as well...

I've never understood why someone didn't implement a Firefox Sync extension for Chrome or vice-versa. Is it technical or are people opinionated enough about browsers that no one has the personal need to develop such extensions?

Re:Private by Design: How We Built Firefox Sync by yoklov on Tuesday November 13, 2018 @11:56PM (#18447613)
For firefox sync on chrome: It’s completely possible, but the crypto is enough of a pain in the ass to deter most people.

(It’s also going to be very difficult to implement a robust sync system this way, integration with the underlying storage is all but required for that)

Re:Private by Design: How We Built Firefox Sync by drdaeman on Wednesday November 14, 2018 @02:26AM (#18448179)
In my opinion, crypto is the easy part. I think the only problem I had when I worked on my own Accounts&Sync re-implementation (a crude hack, I admit) was some MAC-related issue with BrowserID, where different (old) Firefox versions had generated different assertions. Don't really remember what it was.

The real problem is data model is significantly different. It's possible, but a lot of boring work, designing the appropriate transformations.

Re:Private by Design: How We Built Firefox Sync by drdaeman on Wednesday November 14, 2018 @02:22AM (#18448165)
Chrome sync can be also self-hosted, and while I'm not sure how things are today I'd say it used to be significantly easier to self-host.

https://superuser.com/questions/614744/how-to-set-up-a-own-c...