0.21.0

The E2EE encryption V2 format has been reverted. That was probably the cause of the glitch.
Instead, to maintain efficiency, files are treated with Blob until just before saving. Along with this, the old-fashioned encryption format has also been discontinued.
There are both forward and backwards compatibilities, with recent versions. However, unfortunately, we lost compatibility with filesystem-livesync or some.
It will be addressed soon. Please be patient if you are using filesystem-livesync with E2EE.

Changes and performance improvements:

• Now the saving files are processed by Blob.
• The V2-Format has been reverted.
• New encoding format has been enabled in default.
• WARNING: Since this version, the compatibilities with older Filesystem LiveSync have been lost.

Fixed

• To better replication, path obfuscation is now deterministic even if with E2EE.

Fixed

• Now empty file could be decoded.
• Local files are no longer pre-saved before fetching from a remote database.
• No longer deadlock while applying customisation sync.
• Configuration with multiple files is now able to be applied correctly.
• Deleting folder propagation now works without enabling the use of a trash bin.

Fixed

• Now the files which having digit or character prefixes in the path will not be ignored.

Note: I am still wondering why some devices hang up... I will reply today.

Fixed

• The text-input-dialogue is no longer broken.
  • Finally, we can use the Setup URI again on mobile.

New feature:

• We can launch Customization sync from the Ribbon if we enabled it.

Fixed:

• Setup URI is now back to the previous spec; be encrypted by V1.
  • It may avoid the trouble with iOS 17.
• The Settings dialogue is now registered at the beginning of the start-up process.
  • We can change the configuration even though LiveSync could not be launched in normal.

Improved:

• Enumerating documents has been faster.

Sorry for the frequent and thoughtless updates!

New feature:

• We can delete all data of customization sync from the Delete all customization sync data on the Hatch pane.

Fixed(again):

• Prevent keep restarting on iOS by yielding microtasks.

• Fixed:
  • No more UI freezing and keep restarting on iOS.
  • Diff of Non-markdown documents are now shown correctly.
• Improved:
  • Performance has been a bit improved.
  • Customization sync has gotten faster.
    • However, We lost forward compatibility again (only for this feature). Please update all devices.
• Misc
  • Terser configuration has been more aggressive.

0.20.0 Self-hosted LiveSync; Also effective for binaries.

At 0.20.0, Self-hosted LiveSync has changed the binary file format and encrypting format, for efficient synchronisation.
The dialogue will be shown and asks us to decide whether to keep v1 or use v2. Once we have enabled v2, all subsequent edits will be saved in v2. Therefore, devices running 0.19 or below cannot understand this and they might say that decryption error. Please update all devices.
Then we will see an impressibly performant synchronisation.

Of course, these are very impactful changes. If you have any questions or troubled things, please feel free to open an issue and mention me.

Note: if you want to roll it back to v1, please enable Use binary and encryption version 1 on the Hatch pane and perform the rebuild everything once.
Note2 (Updated): If your Obsidian on iPhone keeps restarting, please disable Customization Sync for now.

Extra but notable information:

This format change gives us the ability to detect some marks in the binary files as same as text files. Therefore, we can split binary files and some specific sort of them (i.e., PDF files) at the specific character. It means that editing the middle of files could be detected with marks.

As a result, now only a few chunks are transferred, even if we add a comment to the PDF or put new files into the ZIP archives.

Improved:

• We can open the log pane also from the command palette now.
• Now, the hidden file scanning interval could be configured to 0.
• Check database configuration now points out that we do not have administrator permission.