0.23.0

I am so sorry that I have been a bad correspondent for a while. However, I bring here some very great news today.

Incredibly new features: Object Storage supported!

Now, we can use object storage (MinIO, S3, R2 or anything you like) for synchronising! Moreover, despite that, we can use all the features as if we were using CouchDB.
Note: As this is a pretty experimental feature, hence we have some limitations.

• This is built on the append-only architecture. It will not shrink used storage if we do not perform a rebuild.
• A bit fragile. However, our version x.yy.0 is always so.
• When the first synchronisation, the entire history to date is transferred. For this reason, it is preferable to do this under the WiFi network.
• Do not worry, from the second synchronisation, we always transfer only differences.
• And, “Live” sync is not yet.

I hope this feature empowers users to maintain independence and self-host their data, offering an alternative for those who prefer to manage their own storage solutions and avoid having got stuck in the way of a sudden change in business model.

Of course, I use Self-hosted MinIO for testing and recommend this. It is for the same reason as using CouchDB. -- open, controllable, auditable and indeed already audited by numerous eyes.

Let me write one more acknowledgement.

I have a lot of respect for that plugin, even though it is sometimes treated as if it is a competitor, remotely-save. I think it is a great architecture that embodies a different approach to my approach of recreating history. This time, with all due respect, I have used some of its code as a reference.
Hooray for open source, and generous licences, and the sharing of knowledge by experts.

0.22.19

Fixed:

• No longer data corrupting due to false BASE64 detections.

Improved:

• A bit more efficient in Automatic data compression.

Now, we are ready to fix LiveSync-Bridge and some more.

0.22.18

New feature (Very Experimental):

• Now we can use Automatic data compression to reduce amount of traffic and the usage of remote database.
  • Please make sure all devices are updated to v0.22.18 before trying this feature.
  • If you are using some other utilities which connected to your vault, please make sure that they have compatibilities.
  • Note: Setting File Compression on the remote database works for shrink the size of remote database. Please refer the Doc.

0.22.17:

Fixed:

• Error handling on booting now works fine.
• Replication is now started automatically in LiveSync mode (#398).
• Batch database update is now disabled in LiveSync mode.
• No longer automatically reconnection while off-focused.
• Status saves are thinned out.
• Now Self-hosted LiveSync waits for all files between the local database and storage to be surely checked.

Improved:

• The job scheduler is now more robust and stable (Possibly works for #399, #401) .
• The status indicator no longer flickers and keeps zero for a while.
• No longer meaningless frequent updates of status indicators.
• Now we can configure regular expression filters in handy UI. Thank you so much, @eth-p! (#402)
• Fetch or Rebuild everything is now more safely performed.

Minor things

• Some utility function has been added.
• Customisation sync now less wrong messages.
• Digging the weeds for eradication of type errors.

0.22.16

Fixed:

• Fixed the issue that binary files were sometimes corrupted.
• Fixed customisation sync data could be corrupted.
  • Please let me know if you find anything strange about these two fixes. It is getting a bit complicated in this area.

Improved:

• Now the remote database costs lower memory. (#382)
  • This release requires a brief wait on the first synchronisation, to track the latest changeset again.
• Description added for the Device name. (#391)

Refactored:

• Many type-errors have been resolved.
• Obsolete file has been deleted.

0.22.15

Improved:

• Faster start-up by removing too many logs which indicates normality
• By streamlined scanning of customised synchronisation extra phases have been deleted.

0.22.14:

New feature:

• We can disable the status bar in the setting dialogue.

Improved:

• Now some files are handled as correct data type.
• Customisation sync now uses the digest of each file for better performance.
• The status in the Editor now works performant.

Refactored:

• Common functions have been ready and the codebase has been organised.
• Stricter type checking following TypeScript updates.
• Remove old iOS workaround for simplicity and performance.

0.22.13:

Improved:

• Now using HTTP for the remote database URI warns of an error (on mobile) or notice (on desktop).

Refactored:

• Dependencies have been polished.

0.22.12

Changed:

• The default settings has been changed.

Improved:

• Default and preferred settings are applied on completion of the wizard.

Fixed:

• Now Initialisation Fetch will be performed smoothly and there will be fewer conflicts.
• No longer stuck while Handling transferred or initialised documents.

0.22.11

Fixed:

• Verify and repair all files is no longer broken.

New feature:

• Now Verify and repair all files can...
  • Restore if the file is only in the local database.
  • Show the history.

Improved:

• Performance improved.