bump

manifest.json

@@ -1,7 +1,7 @@
 {
     "id": "obsidian-livesync",
     "name": "Self-hosted LiveSync",
-    "version": "0.21.5",
+    "version": "0.22.0",
     "minAppVersion": "0.9.12",
     "description": "Community implementation of self-hosted livesync. Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
     "author": "vorotamoroz",

package-lock.json

@@ -1,12 +1,12 @@
 {
     "name": "obsidian-livesync",
-    "version": "0.21.5",
+    "version": "0.22.0",
     "lockfileVersion": 2,
     "requires": true,
     "packages": {
         "": {
             "name": "obsidian-livesync",
-            "version": "0.21.5",
+            "version": "0.22.0",
             "license": "MIT",
             "dependencies": {
                 "diff-match-patch": "^1.0.5",

package.json

@@ -1,6 +1,6 @@
 {
     "name": "obsidian-livesync",
-    "version": "0.21.5",
+    "version": "0.22.0",
     "description": "Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
     "main": "main.js",
     "type": "module",

updates.md

@@ -1,43 +1,22 @@
-### 0.21.0
+### 0.22.0
-The E2EE encryption V2 format has been reverted. That was probably the cause of the glitch.
+A few years passed since Self-hosted LiveSync was born, and our codebase had been very complicated. This could be patient now, but it should be a tremendous hurt.
-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.
+Therefore at v0.22.0, for future maintainability, I refined task scheduling logic totally.
-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.
 
+Of course, I think this would be our suffering in some cases. However, I would love to ask you for your cooperation and contribution.
+
+Sorry for being absent so much long. And thank you for your patience!
+
+Note: we got a very performance improvement.
 
 #### Version history
-- 0.21.5
+- 0.22.0
-  - Improved:
+  - Refined:
-    - Now all revisions will be shown only its first a few letters.
+    - Task scheduling logics has been rewritten.
-    - Now ID of the documents is shown in the log with the first 8 letters.
+    - Possibly many bugs and fragile behaviour has been fixed
   - Fixed:
-    - Check before modifying files has been implemented.
+    - Remote-chunk-fetching now works with keeping request intervals
-    - Content change detection has been improved.
+  - New feature:
-- 0.21.4
+    - We can show only the icons in the editor.
-  - This release had been skipped.
+
-- 0.21.3
-  - Implemented:
-    - Now we can use SHA1 for hash function as fallback.
-- 0.21.2
-  - IMPORTANT NOTICE: **0.21.1 CONTAINS A BUG WHILE REBUILDING THE DATABASE. IF YOU HAVE BEEN REBUILT, PLEASE MAKE SURE THAT ALL FILES ARE SANE.**
-    - This has been fixed in this version.
-  - Fixed:
-    - No longer files are broken while rebuilding.
-    - Now, Large binary files can be written correctly on a mobile platform.
-    - Any decoding errors now make zero-byte files.
-  - Modified:
-    - All files are processed sequentially for each.
-- 0.21.1
-  - Fixed:
-    - No more infinity loops on larger files.
-    - Show message on decode error.
-  - Refactored:
-    - Fixed to avoid obsolete global variables.
-- 0.21.0
-  - 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.
 
 ... To continue on to `updates_old.md`.

updates_old.md

@@ -1,3 +1,43 @@
+### 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.
+
+- 0.21.5
+  - Improved:
+    - Now all revisions will be shown only its first a few letters.
+    - Now ID of the documents is shown in the log with the first 8 letters.
+  - Fixed:
+    - Check before modifying files has been implemented.
+    - Content change detection has been improved.
+- 0.21.4
+  - This release had been skipped.
+- 0.21.3
+  - Implemented:
+    - Now we can use SHA1 for hash function as fallback.
+- 0.21.2
+  - IMPORTANT NOTICE: **0.21.1 CONTAINS A BUG WHILE REBUILDING THE DATABASE. IF YOU HAVE BEEN REBUILT, PLEASE MAKE SURE THAT ALL FILES ARE SANE.**
+    - This has been fixed in this version.
+  - Fixed:
+    - No longer files are broken while rebuilding.
+    - Now, Large binary files can be written correctly on a mobile platform.
+    - Any decoding errors now make zero-byte files.
+  - Modified:
+    - All files are processed sequentially for each.
+- 0.21.1
+  - Fixed:
+    - No more infinity loops on larger files.
+    - Show message on decode error.
+  - Refactored:
+    - Fixed to avoid obsolete global variables.
+- 0.21.0
+  - 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.
+
 ## 0.20.0
 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.