API v20190520 migration

[moughxyz]

Hey Tanner, here are some instructions for how to update to the latest API version: https://github.com/standardfile/sfjs/wiki/Migrating-to-API-version-20190520.

Clients not updated to this will continue to use the older API version, which should be fine for the most part, except you'll miss out on fine-grained improvements to conflict resolution.

[tannercollin]

Thanks for the info, Mo!
I haven't touched snfs in a while, but will tackle this with the next set of changes.

[jonhadfield]

URL above isn't working. @mobitar I assume this is the latest:
https://github.com/standardnotes/snjs/blob/004/specification.md#003-migration

[moughxyz]

I suppose this issue is more related to API version migration, rather than client-side SNJS protocol version migration. Currently servers don't really need to change anything for the new system.

[rdhyee]

@mobitar I'm working on implementing 004 for snfs (#32) -- right now snfs is on v20190520. I believe that I will need to update snfs to v20200115 before/while implementing encryption version 004. Do you have any documentation on how to migrate from v20190520 to v20200115? Thanks.

[moughxyz]

There's no changes necessary on the client side to use the new server API version. Just pass the new version to the server indicating you'd like to use that version.

[rdhyee]

@mobitar Thanks. I confirm that changing the API version from 20190520 to 20200115 seems to just work for snfs -- c8b675a -- now on to integrating 004 into 003 (#32)

@tannercollin This issue should probably be closed now.