21–30 of 180 posts
I would like to see an option 4:
Option 4: The server side of sync is open sourced, and I can run it on my own machine, and point my browsers at my personal instance. Then no data is ever on Mozilla's servers.
> Other approaches > [ list of 3 options ] I would like to see an option 4: Option 4: The server side of sync is open sourced, and I can run it on my own machine, and point my browsers at my personal instance. Then no data is ever on Mozilla's servers.
I have not set it up yet. But is this not what you are looking for ?
https://mozilla-services.readthedocs.io/en/latest/howtos/run...
> Other approaches > [ list of 3 options ] I would like to see an option 4: Option 4: The server side of sync is open sourced, and I can run it on my own machine, and point my browsers at my personal instance. Then no data is ever on Mozilla's servers.
This still uses FxA for authentication. You can self-host that up as well, but it's not nearly as straightforward, and I'm not aware of good documentation on how to do so.
> Other approaches > [ list of 3 options ] I would like to see an option 4: Option 4: The server side of sync is open sourced, and I can run it on my own machine, and point my browsers at my personal instance. Then no data is ever on Mozilla's servers.
I was just looking into this. I thought it was? I have not set it up yet. But is this not what you are looking for ? https://mozilla-services.readthedocs.io/en/latest/howtos/run...
The harder aspect comes with the Firefox accounts server, as that requires a bit more configuration and deployment.
I would be very interested in seeing someone build a docker-composer setup for this, such that it can be automatically deployed for those who don't have the time/skills to set it up.
Earlier quoted context omitted.
Doesn't chrome lets you use your own encryption key?
Yes, but it's not the default. From the article: > One could, however, add a second passphrase that is never sent to the server, and encrypt the data using that. Chrome provides this as a non-default option. The average user doesn't have the expertise to know that they have to configure an additional "master password" to keep Google from mining their data for ads.
I just got this morbid idea of Google mining storing passwords to recommend LastPass/1Password in ads based on your password strength.
Earlier quoted context omitted.
Yes, sort of (more about the process: https://github.com/mozilla/fxa-auth-server/wiki/onepw-protoc... ). Key difference: you don't need to sync all the data up again, since there's a separate key for that, which doesn't change. That said, if you forget your password you do lose remote synced data. The hope is that you have at least one device connected that still has the data, which will upload it in that case. This…
You seem to know a bit about encryption. Which is why it baffles me- how does telegram do this? Does it need a connected device in this way too? So one can upload the encryption key if its lost? If no device is connected, can/how do they do it? If yes, can Firefox copy that way?
>how does telegram do this?
...the short answer is they don't.
Earlier quoted context omitted.
Yes, but it's not the default. From the article: > One could, however, add a second passphrase that is never sent to the server, and encrypt the data using that. Chrome provides this as a non-default option. The average user doesn't have the expertise to know that they have to configure an additional "master password" to keep Google from mining their data for ads.
>keep Google from mining their data for ads I just got this morbid idea of Google mining storing passwords to recommend LastPass/1Password in ads based on your password strength.
The fact that containers don't sync well is probably my biggest frustration with Firefox at the moment.
I’ve been using Firefox since I heard about their containers. I’m happy they are pushing for all these privacy tools. For me these are the features that will make me chose over chrome.
- It can be integrated into Google Chrome on desktop operating systems.
- It can be provided as a stand-alone app on iOS so that I can:
a) “Share” links to this hypothetical stand-alone Sync app from Safari in order to send them to Firefox Sync bookmarks storage.
b) Copy username and password from the stand-alone Sync app when using Safari on iOS.
It might sound like a peculiar setup but bear with me.
The situation is that I run Firefox as the main browser on my laptop, Chromium as main browser on desktop and Safari as main browser on iOS.
For a long time I’ve used Firefox Sync as the “main” storage of passwords, and I would go into Firefox settings and copy username and password from there on desktop and mobile. Even though I store the passwords and usernames in the other browsers on first login it’s still a bit cumbersome whenever I add a new account, log in for the first time, or change a password.
Recently on desktop I started using KeePassXC on my desktop and the browser plugins for it in order to make it a bit smoother. Today I installed MiniKeePass on iOS and am going to find a good way of keeping it in sync with my desktop. In the end though, KeePassXC is not quite what I want, whereas the core of Firefox Sync is exactly what I want.
As for my bookmarks, they are all over the place. Some in Firefox, some in Chromium, some in Safari, some in exported files or copies of old homedirs, and a lot of bookmarks probably lost at various points in time. Again, the core of Firefox Sync is what I want.