4 ms·

Sync is nothing but an awfully overengineered blob storage (I have implemented an alternative Accounts+Sync server when 1.5 came out, https://gitlab.com/drdaema

Sync is nothing but an awfully overengineered blob storage (I have implemented an alternative Accounts+Sync server when 1.5 came out, https://gitlab.com/drdaeman/firesync/ https://gitlab.com/drdaeman/firesync/ - long abandoned and the code is awful proof-of-concept inly, but the point here is to prove that I have a slightly educated opinion on the matter). IMHO, It would be best (for technical users) if Firefox forks would rather replace Sync with something more standard like S3 or WebDAV. If my memory serves me right, there’s absolutely nothing in Sync that those protocols cannot do equally well (and even better because they’re actual mostly-interoperable standards). Heck, it would be nice if Mozilla would do the same thing, but I’m afraid NIH is way too strong with them. I’m very happy if that gives us Rust, but Sync is simply garbage that shouldn’t have been ever made.

63stack 2y ago
Is there a specification somewhere for the sync server that you followed, or did you figure out the endpoints/logic by looking at mozilla's sync server? I was thinking about taking a crack at this as well, but I can't find a spec, and I want to leave looking at the python/rust sync server source code as a last resort.
- layer8 2y ago
  The API docs are linked here: https://github.com/mozilla-services/syncstorage-rs?tab=readme-ov-file#related-documentation https://github.com/mozilla-services/syncstorage-rs?tab=readm...
- drdaeman 2y ago
  It is documented here: https://mozilla-services.readthedocs.io/en/latest/storage/apis-1.5.html https://mozilla-services.readthedocs.io/en/latest/storage/ap... I'm not sure about the current status of this document. Years ago there were subtle nuances that I gad to reverse engineer looking at the source code and Firefox's actual behavior.
layer8 2y ago
With only object storage, handling sync conflicts [0] becomes more complicated. I can understand why they don’t do that. [0] https://mozilla-services.readthedocs.io/en/latest/storage/apis-1.5.html#syncstorage-concurrency https://mozilla-services.readthedocs.io/en/latest/storage/ap...
- AshamedCaptain 2y ago
  Yet stuff like CalDAV which is used by millions transparently handles syncing on top of WebDAV (arguably not just dumb storage , but not much better than it). Not only that, but Firefox Sync _itself_ used to be WebDAV.

63stack 2y ago

Is there a specification somewhere for the sync server that you followed, or did you figure out the endpoints/logic by looking at mozilla's sync server? I was thinking about taking a crack at this as well, but I can't find a spec, and I want to leave looking at the python/rust sync server source code as a last resort.

layer8 2y ago
The API docs are linked here: https://github.com/mozilla-services/syncstorage-rs?tab=readme-ov-file#related-documentation https://github.com/mozilla-services/syncstorage-rs?tab=readm...
drdaeman 2y ago
It is documented here: https://mozilla-services.readthedocs.io/en/latest/storage/apis-1.5.html https://mozilla-services.readthedocs.io/en/latest/storage/ap... I'm not sure about the current status of this document. Years ago there were subtle nuances that I gad to reverse engineer looking at the source code and Firefox's actual behavior.

layer8 2y ago

With only object storage, handling sync conflicts [0] becomes more complicated. I can understand why they don’t do that. [0] https://mozilla-services.readthedocs.io/en/latest/storage/apis-1.5.html#syncstorage-concurrency https://mozilla-services.readthedocs.io/en/latest/storage/ap...

AshamedCaptain 2y ago
Yet stuff like CalDAV which is used by millions transparently handles syncing on top of WebDAV (arguably not just dumb storage , but not much better than it). Not only that, but Firefox Sync _itself_ used to be WebDAV.