0.24.0.dev-rc5

0.24.0.dev-rc5

I have been beginning to think that releasing dev is a good idea. Thank you for your patience with the fragile state.

Improved

• A note relating to device names has been added to Customisation Sync on the setting dialogue.
• Logs of Hidden File Sync and Customisation Sync have been prefixed with the respective feature names.

Fixed

• Hidden file sync is now working correctly.
• Customisation Sync is now working correctly together with hidden file sync
• No longer database suffix is stored in the setting sharing markdown.

0.24.0.dev-rc4

0.24.0.dev-rc4

Improved

• The welcome message is now more simple to encourage the use of the Setup-URI.
  • And the secondary message is also simpler to guide users to Minimal Setup.
    • But Setup-URI will be recommended again, due to its importance.
  • These dialogues contain a link to the documentation which can be clicked.
• The minimal setup is more minimal now. And, the setup is more user-friendly.
  • Now the Configuration of the remote database is checked more robust, but we can ignore the warning and proceed with the setup.
• Before we are asked about each feature, we are asked if we want to use optional features in the first place.
  • This is to prevent the user from being overwhelmed by the features.
  • And made it clear that it is not recommended for new users.
• Many messages have been improved for better understanding.
  • Ridiculous messages have been (carefully) refined.
  • Dialogues are more informative and friendly.
    • A lot of messages have been mostly rewritten, leveraging Markdown.
    • Especially auto-closing dialogues are now explicitly labelled: To stop the countdown, tap anywhere on the dialogue.
• Now if the is plugin configured to ignore some events, we will get a chance to fix it, in addition to the warning.
  • And why that has happened is also explained in the dialogue.

Fixed

• While restarting the plug-in, the shown dialogues will be automatically closed to avoid unexpected behaviour.
• Replicated documents that the local device has configured to ignore are now correctly ignored.
• The chunks of the document on the local device during the first transfer will be created correctly.
  • And why we should create them is now explained in the dialogue.
• If optional features have been enabled in the wizard, Enable advanced features will be toggled correctly.

Changed

• Some default settings have been changed for easier new user experience.
  • Preventing the meaningless migration of the settings.

Tidied

• Commented-out codes have been gradually removed.

0.24.0.dev-rc3

0.24.0 RC Release Note

Over the past three years since the inception of the plugin, various features have been implemented to address diverse user needs. This is so honourable and I am grateful for your years of support.
However, However, this process has resulted in a codebase that has become increasingly disorganised, with features becoming entangled.

Consequently, this has led to a situation where bugs can go unnoticed or resolving one issue may inadvertently introduce another.

In 0.24.0, I reorganised the previously disjointed main codebase into clearly defined modules. Although I anticipated that the overall volume of code would not increase, I discovered that it has, in fact, expanded. While the complexity may still be considerable, the refactoring has enhanced clarity regarding the current structure of the code. (The next focus may involve a review of dependencies).

Throughout this process, a significant number of bugs have been resolved. And it may be worth mentioning that these bugs may had given rise to other bugs. I kindly request that you verify whether your issues have been addressed. At least conflict resolution and related issues have improved significantly.

It is also the first step towards a fully-fledged-fancy LiveSync, not just a plug-in from Obsidian. Of course, it will still be a plug-in as a first class and foremost, but this development marks a significant step towards the self-hosting concept.

This dev release is very close to the beta version that I had previously indicated would not be released. As a result, I have faced challenges in maintaining the main branch while working on this dev release. Regrettably, I have not been able to make any commits to the main branch in the last three weeks. Thus, the dev branch will remain reserved for major changes only.

The Release Candidate will be available for a few days and will only be officially released once users, including myself, have confirmed that there are no issues.

Finally, I would like to once again express my respect and gratitude to all of you once again. Thank you for your interest in the development version. Your contributions and dedication are greatly appreciated through testing.

As you already know, you can install this release candidate via BRAT.

Thank you, and I hope your troubles will be resolved!

0.23.23

0.23.23:

Refined:

• Setting dialogue very slightly refined.
  • The hodgepodge inside the Hatch pane has been sorted into more explicit categorised panes.
    • Now we have new panes for:
      • Selector
      • Advanced
      • Power users
      • Patches (Edge case)
  • Applying the settings will now be more informative.
    • The header bar will be shown for applying the settings which needs a database rebuild.
    • Applying methods are now more clearly navigated.
  • Definitely, drastic change. I hope this will be more user-friendly. However, if you notice any issues, please let me know. I hope that nothing missed.

New features:

• Word-segmented chunk building on users language
  • Chunks can now be built with word-segmented data, enhancing efficiency for markdown files which contains the multiple sentences in a single line.
  • This feature is enabled through Use Segmented-splitter.
    • (Default: Disabled, Please be relived, I have learnt).

Fixed:

• Sending chunks on Send chunk in bulk are now buffered to avoid the out-of-memory error.
• Send chunk in bulk is back to default disabled. (Sorry, not applied to the migrated users; I did not think we should deepen the wound any further "automatically").
• Merging conflicts of JSON files are now works fine even if it contains null.

Development:

• Implemented the logic for automatically generating the stub of document for the setting dialogue.
• Mangling variable names are now disabled.

0.23.22

0.23.22:

Fixed:

• Case-insensitive file handling
  • Full-lower-case files are no longer created during database checking.
• Bulk chunk transfer
  • The default value will automatically adjust to an acceptable size when using IBM Cloudant.

0.23.21

0.23.21

For the past two months, I have had the privilege of caring for our merciful mother for her departure. I would like to once again express my heartfelt gratitude to all of you. Thank you very much.

This time, I am releasing updates and fixes that have accumulated. I encourage you to install it.

These changes have been gradually implemented in my Vault part by part, day by day. So I do not anticipate any major issues. However, if you encounter anything, please do not hesitate to let me know. And, I apologise for any delays in my responses. I will definitely respond.

I am available on Nostr and Fediverse(https://mozilla.social/@vrtmrz), so feel free to reach out. Please note that my English may be far from perfect, but I would love to try to do my best.

Note: if you are troubled with using IBM Cloudant, please set 1(MB) to Maximum size of chunk send in one request, or disable Send chunks in bulk. Sorry for lacking handling.

New Features:

• Case-insensitive file handling
  • Files can now be handled case-insensitively.
  • This behaviour can be modified in the settings under Handle files as Case-Sensitive (Default: Prompt, Enabled for previous behaviour).
• Improved chunk revision fixing
  • Revisions for chunks can now be fixed for faster chunk creation.
  • This can be adjusted in the settings under Compute revisions for chunks (Default: Prompt, Enabled for previous behaviour).
• Bulk chunk transfer
  • Chunks can now be transferred in bulk during uploads.
  • This feature is enabled by default through Send chunks in bulk.
• Creation of missing chunks without
  • Missing chunks can be created without storing notes, enhancing efficiency for first synchronisation or after prolonged periods without synchronisation.

Improvements:

• File status scanning on the startup
  • Quite significant performance improvements.
  • No more missing scans of some files.
• Status in editor enhancements
  • Significant performance improvements in the status display within the editor.
  • Notifications for files that will not be synchronised will now be properly communicated.
• Encryption and Decryption
  • These processes are now performed in background threads to ensure fast and stable transfers.
• Verify and repair all files
  • Got faster through parallel checking.
• Migration on update
  • Migration messages and wizards have become more helpful.

Behavioural changes:

• Chunk size adjustments
  • Large chunks will no longer be created for older, stable files, addressing storage consumption issues.
• Flag file automation
  • Confirmation will be shown and we can cancel it.

Fixed:

• Database File Scanning
  • All files in the database will now be enumerated correctly.

Miscellaneous

• Dependency updated.
• Now, tree shaking is left to terser, from esbuild.

0.23.20

0.23.20:

Fixed:

• Customisation Sync now checks the difference while storing or applying the configuration.
  • No longer storing the same configuration multiple times.
• Time difference in the dialogue has been fixed.
• Remote Storage Limit Notification dialogue has been fixed, now the chosen value is saved.

Improved:

• The Enlarging button on the enlarging threshold dialogue now displays the new value.

0.23.18

0.23.18:

A lot of things have been going on and it has been late. Thank you for your patience. However! Customisation Sync has reached Beta 3.
The screen no longer collapses and it also works very quickly when per-file-saved customisation sync is enabled.

As you probably already know, I often post my daily progress on Fediverse. Many days I only have my smartphone and tablet with me during my free time. Of course, I will reply to issues soon! I always appreciate your posts!

New feature:

• Per-file-saved customization sync has been shipped.
  • We can synchronise plug-ins etc., more smoothly.
  • Default: disabled. We need a small migration when enabling this. And all devices should be updated to v0.23.18. Once we enabled this, we lost compatibility with old versions.
• Customisation sync has got beta3.
  • We can set Flag to each item to select the newest, automatically.
    • This configuration is per device.

Improved:

• Start-up speed has been improved.

Fixed:

• On the customisation sync dialogue, buttons are kept within the screen.
• No more unnecessary entries on data.json for customisation sync.
• Selections are no longer lost while updating customisation items.

Tidied on source codes:

• Many typos have been fixed.
• Some unnecessary type casting removed.

0.23.17

0.23.17:

Note: Updated the dependencies, please let me know if you have got troubled especially on the traditional devices.

Improved:

• Overall performance has been improved by using PouchDB 9.0.0.
• Configuration mismatch detection is refined. We can resolve mismatches more smoothly and naturally.
  More detail is on troubleshooting.md on the repository.

Fixed:

• Customisation Sync will be disabled when a corrupted configuration is detected.
  Therefore, the Device Name can be changed even in the event of a configuration mismatch.

New feature:

• We can get a notification about the storage usage of the remote database.
  • Default: We will be asked.
  • If the remote storage usage approaches the configured value, we will be asked whether we want to Rebuild or increase the limit.

0.23.16

0.23.16:

Maintenance Update:

• Library refining (Phase 1 - step 2). There are no significant changes on the user side.
• Including the following fixes of potentially problems:
  • the problem which the path had been obfuscating twice has been resolved.
    • Note: potential problems of the library; which has not happened in Self-hosted LiveSync for some reasons. However, it could have occurred in LiveSync-Hub.