- cross-posted to:
- selfhosted
- linux
- [email protected]
- cross-posted to:
- selfhosted
- linux
- [email protected]
This repository is holding a working docker-compose setup for documentation pourpuses because syncstorage-rs’s documentation is not very good to explain how to self host the new rust syncserver.
With help of it you can self host the new Firefox sync server, which is written in Rust and replaces the old python one, which is deprecated.
I’ve been looking for this just yesterday but apparently all sync info is end to end encrypted anyways and Mozilla has no access to the synchronized data? Is there a reason to self host this but just for the principle of it?
If you have multiple firefox profiles, then you have to create an sync account for each one if you want to sync. Not a good idea if you have 5 profiles, some of them using a main email (like a corp or school) that won’t be around forever.
Being able to sync multiple profiles with only one account is convenient for me.
Why should storing your browser history and behaviour with a 3rd party in a 3rd country in a procured 3rd party cloud infra provider and a 3rd party colocation provider be the default? Why not keep that personal information just inside, instead of letting it leave out of the front door? Also, encryption has more to do with confidentiality than security. If someone gets access to your encrypted data all they have to do is encrypt it again, to do harm.