Skip to content

0.5.0

Choose a tag to compare

@seking seking released this 26 Oct 14:41

Google Drive is now a place to sync to, beside GitHub and Dropbox. Under "Connection" in the settings, "Service" chooses between them. Connecting is done with a code you enter on Google's page, and Sync Evo reaches only the files it made itself, in a Sync Evo folder in your My Drive. See "Google Drive" in the README before you use it.

  • With Google Drive, a conflict is not merged: the file takes the version from Google Drive, and this device's version is kept in _conflicts/.
  • Automatic sync with Google Drive runs no more often than every 5 minutes.
  • When the requests Google allows Sync Evo for a day, shared by all its users, run out, Sync Evo stops and holds automatic sync until midnight, Pacific time.

All of Sync Evo is still free. Syncing with Dropbox and Google Drive may need a license key later. Any paid plan will be announced in the README and the release notes before it starts, and even then, Dropbox and Google Drive stay free for 3 months from the day it starts, or from your first sync with the account, if that is later.

The license has changed. Dropbox, Google Drive and the license key check are now in pro/, under the Elastic License 2.0. It is source-available: you may read, change and share it, but not change, remove or get around the license key check, not remove its notices, and not offer it as a hosted service. The rest stays under the GNU AGPL 3.0. See LICENSE.

Also in this version:

  • Android: a rename that changes only the case of a name is now made on Android too. A folder renamed this way may show under its old spelling as well until Obsidian is restarted: do not delete that one, as it deletes the real folder.
  • An upload no longer stops at a path on this device that cannot be read, such as a link another app left in the vault. The path is reported and left as it is.
  • An upload to an empty remote no longer asks first, except to a GitHub repository that is public, or that Sync Evo could not tell is private. The rules Sync Evo wrote to .gitignore are folded into one line in the questions before an upload.
  • Every upload tells which new files differ from others only in case, as some devices cannot tell such paths apart.
  • A vault with a .git folder at its root is told to use Git or Sync Evo on a device, not both.
  • A sync started before the settings are ready says what is missing, with a button that opens the settings.
  • "Start over" in the settings is now "Reset settings". The command "Start over", which downloads everything again, keeps its name.
  • A copy of the sync log starts with the versions, the device and the service, and tells each wait before a request was sent again.
  • The README and the docs are in Japanese too, with a FAQ, a page on choosing a service, and how to report a bug or a security problem.

0.4.0 is not on the releases page any more, so there is no going back to it from 0.5.0. A vault set to Google Drive could not be synced by 0.4.0 anyway.

See the README for the details.