Since we’re using our own webdav back-end for synchronization, it would be nice to have documented what the client expects from the webdav server.
Currently AFAIR I’m supporting GET, PUT and PROPFIND, serving the notes as a flat directory of some_hash_string.md files plus the two directories .sync and .resource, the last of which contains resources pointed to by the md files. The md files themselves contain metadata at the end, in the form of key:value lines. One key is _type, with values 1-5, with 1 indicating a normal note, 2 indicating a folder, 4 a media resource (with id indicating the corresponding file in the .resource directory) etc.
Again, it would be really nice to have this API documented and changes to it announced well in advance of updating the clients.
Currently I don’t expect our back-end to support the updated clients, so I recommend users to not upgrade.
Thanks for your efforts,