mirror of
https://github.com/vrtmrz/obsidian-livesync.git
synced 2026-01-27 07:27:13 +00:00
56 lines
3.4 KiB
Markdown
56 lines
3.4 KiB
Markdown
### 0.23.0
|
|
Incredibly new features!
|
|
|
|
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.
|
|
|
|
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 being stuck on the right side 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.
|
|
|
|
#### Version history
|
|
- 0.23.19:
|
|
- 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.
|
|
- 0.23.18:
|
|
- New feature:
|
|
- Per-file-saved customization sync has been shipped.
|
|
- We can synchronise plug-igs 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:
|
|
- 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.
|
|
|
|
Older notes is in [updates_old.md](https://github.com/vrtmrz/obsidian-livesync/blob/main/updates_old.md). |