Sync-1.5 and Accounts. I used to run Sync-1.0 and it was okay. At least I didn't have to bother about protocol details. And now, even though it's FLOSS, it's st

Sync-1.5 and Accounts. I used to run Sync-1.0 and it was okay. At least I didn't have to bother about protocol details. And now, even though it's FLOSS, it's still unmaintained abandonware so I don't think it's a good target. 1.5 is very different to 1.0. Just consider the fact that to log in to Accounts and use Sync you need to use three auth protocols: HAWK, OAuth2 and BrowserID. And serve a webpage with some custom JS (that iOS version for some reason would reject to load). And Sync alone is full of proprietary[1] stuff like X-Weave-Timestamp headers, application/newlines MIME type (seriously, not even a vendor extension), etc. It could've easily been WebDAV plus a few small protocol extensions where things didn't fit well. It is not. ____ [1] "Proprietary" as in "unique to this project, neither used by anything else, nor usable by anything else because it's poorly documented moving target without change warnings" not as in "non-FLOSS".