6.6 KiB
0.24.29
Fixed
- Synchronisation with buckets now works correctly, regardless of whether a prefix is set or the bucket has been (re-) initialised (#664).
- An information message is now displayed again, during any automatic synchronisation is enabled (#662).
Tidied up
- Importing paths have been tidied up.
0.24.28
Fixed
- Batch Update is no longer available in LiveSync mode to avoid unexpected behaviour. (#653)
- Now compatible with Cloudflare R2 again for bucket synchronisation.
- @edo-bari-ikutsu, thank you for your contribution!
- Prevention of broken behaviour due to database connection failures added (#649).
0.24.27
Improved
- We can use prefix for path for the Bucket synchronisation.
- For example, if you set the
vaultName/as a prefix for the bucket in the root directory, all data will be transferred to the bucket under thevaultName/directory.
- For example, if you set the
- The "Use Request API to avoid
inevitableCORS problem" option is now promoted to the normal setting, not a niche patch.
Fixed
- Now switching replicators applied immediately, without the need to restart Obsidian.
Tidied up
- Some dependencies have been updated to the latest version.
0.24.26
This update introduces an option to circumvent Cross-Origin Resource Sharing (CORS) constraints for CouchDB requests, by leveraging Obsidian's native request API. The implementation of such a feature had previously been deferred due to significant security considerations.
CORS is a vital security mechanism, enabling servers like CouchDB -- which functions as a sophisticated REST API -- to control access from different origins, thereby ensuring secure communication across trust boundaries. I had long hesitated to offer a CORS circumvention method, as it deviates from security best practices; My preference was for users to configure CORS correctly on the server-side.
However, this policy has shifted due to specific reports of intractable CORS-related configuration issues, particularly within enterprise proxy environments where proxy servers can unpredictably alter or block communications. Given that a primary objective of the "Self-hosted LiveSync" plugin is to facilitate secure Obsidian usage within stringent corporate settings, addressing these 'unavoidable' user-reported problems became essential. Mostly raison d'être of this plugin.
Consequently, the option "Use Request API to avoid inevitable CORS problem"
has been implemented. Users are strongly advised to enable this only when
operating within a trusted environment. We can enable this option in the Patch pane.
However, just to whisper, this is tremendously fast.
New Features
- Automatic display-language changing according to the Obsidian language
setting.
- We will be asked on the migration or first startup.
- Note: Please revert to the default language if you report any issues.
- Not all messages are translated yet. We welcome your contribution!
- Now we can limit files to be synchronised even in the hidden files.
- "Use Request API to avoid
inevitableCORS problem" has been implemented.- Less secure, please use it only if you are sure that you are in the trusted
environment and be able to ignore the CORS. No
Web vieweror similar tools are recommended. (To avoid the origin forged attack). If you are able to configure the server setting, always that is recommended.
- Less secure, please use it only if you are sure that you are in the trusted
environment and be able to ignore the CORS. No
Show status icon instead of file warnings bannerhas been implemented.- If enabled, the ⛔ icon will be shown inside the status instead of the file warnings banner. No details will be shown.
Improved
- All regular expressions can be inverted by prefixing
!!now.
Fixed
- No longer unexpected files will be gathered during hidden file sync.
- No longer broken
\nand new-line characters during the bucket synchronisation. - We can purge the remote bucket again if we using MinIO instead of AWS S3 or Cloudflare R2.
- Purging the remote bucket is now more reliable.
- 100 files are purged at a time.
- Some wrong messages have been fixed.
Behaviour changed
- Entering into the deeper directories to gather the hidden files is now limited
by
/or\/prefixed ignore filters. (It means that directories are scanned deeper than before).- However, inside the these directories, the files are still limited by the ignore filters.
Etcetera
- Some code has been tidied up.
- Trying less warning-suppressing and be more safer-coding.
- Dependent libraries have been updated to the latest version.
- Some build processes have been separated to
preandpostprocesses.
0.24.25
Improved
- Peer-to-peer synchronisation has been got more robust.
Fixed
- No longer broken falsy values in settings during set-up by the QR code generation.
Refactored
- Some
windowreferences now have pointed toglobalThis. - Some sloppy-import has been fixed.
- A server side implementation
Synchromeshhas been suffixed withdenoinstead ofservernow.
0.24.24
Fixed
- No longer broken JSON files including
\n, during the bucket synchronisation. (#623) - Custom headers and JWT tokens are now correctly sent to the server during configuration checking. (#624)
Improved
- Bucket synchronisation has been enhanced for better performance and
reliability.
- Now less duplicated chunks are sent to the server. Note: If you have
encountered about too less chunks, please let me know. However, you can send
it to the server by
Overwrite remote. - Fetching conflicted files from the server is now more reliable.
- Dependent libraries have been updated to the latest version.
- Also, let me know if you have encountered any issues with this update. Especially you are using a device that has been in use for a little longer.
- Now less duplicated chunks are sent to the server. Note: If you have
encountered about too less chunks, please let me know. However, you can send
it to the server by
0.24.23
New Feature
- Now, we can send custom headers to the server.
- They can be sent to either CouchDB or Object Storage.
- Authentication with JWT in CouchDB is now supported.
- I will describe steps later, but please refer to the CouchDB document.
- A JWT keypair for testing can be generated in the setting dialogue.
Improved
- The QR Code for set-up can be shown also from the setting dialogue now.
- Conflict checking for preventing unexpected overwriting on the boot-up process has been quite faster.
Fixed
- Some bugs on Dev and Testing modules have been fixed.
Older notes are in updates_old.md.