From f6d5b78cc8e246a046b6b52835430cf2212edca3 Mon Sep 17 00:00:00 2001 From: vorotamoroz Date: Mon, 17 Feb 2025 11:35:34 +0000 Subject: [PATCH] bump --- manifest.json | 2 +- package-lock.json | 4 ++-- package.json | 2 +- updates.md | 32 ++++++++++++++++++++++++++++++++ 4 files changed, 36 insertions(+), 4 deletions(-) diff --git a/manifest.json b/manifest.json index b76c86b..6f697fb 100644 --- a/manifest.json +++ b/manifest.json @@ -1,7 +1,7 @@ { "id": "obsidian-livesync", "name": "Self-hosted LiveSync", - "version": "0.24.12", + "version": "0.24.13", "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", diff --git a/package-lock.json b/package-lock.json index cb181b8..1202064 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "obsidian-livesync", - "version": "0.24.12", + "version": "0.24.13", "lockfileVersion": 2, "requires": true, "packages": { "": { "name": "obsidian-livesync", - "version": "0.24.12", + "version": "0.24.13", "license": "MIT", "dependencies": { "@aws-sdk/client-s3": "^3.645.0", diff --git a/package.json b/package.json index 8f8a3fa..0a1c8f7 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "obsidian-livesync", - "version": "0.24.12", + "version": "0.24.13", "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", diff --git a/updates.md b/updates.md index 33fc2c4..d592bcf 100644 --- a/updates.md +++ b/updates.md @@ -10,6 +10,38 @@ Nevertheless, that being said, to be more honest, I still have not decided what Note: Already you have noticed this, but let me mention it again, this is a significantly large update. If you have noticed anything, please let me know. I will try to fix it as soon as possible (Some address is on my [profile](https://github.com/vrtmrz)). +## 0.24.13 + +Sorry for the lack of replies. The ones that were not good are popping up, so I am just going to go ahead and get this one... However, they realised that refactoring and restructuring is about clarifying the problem. Your patience and understanding is much appreciated. + +### Fixed + +#### General Replication + +- No longer unexpected errors occur when the replication is stopped during for some reason (e.g., network disconnection). + +#### Peer-to-Peer Synchronisation + +- Set-up process will not receive data from unexpected sources. +- No longer resource leaks while enabling the `broadcasting changes` +- Logs are less verbose. +- Received data is now correctly dispatched to other devices. +- `Timeout` error now more informative. +- No longer timeout error occurs for reporting the progress to other devices. +- Decision dialogues for the same thing are not shown multiply at the same time anymore. +- Disconnection of the peer-to-peer synchronisation is now more robust and less error-prone. + +#### Webpeer + +- Now we can toggle Peers' configuration. + +### Refactored + +- Cross-platform compatibility layer has been improved. +- Common events are moved to the common library. +- Displaying replication status of the peer-to-peer synchronisation is separated from the main-log-logic. +- Some file names have been changed to be more consistent. + ## 0.24.12 I created a SPA called [webpeer](https://github.com/vrtmrz/livesync-commonlib/tree/main/apps/webpeer) (well, right... I will think of a name again), which replaces the server when using Peer-to-Peer synchronisation. This is a pseudo-client that appears to other devices as if it were one of the clients. . As with the client, it receives and sends data without storing it as a file.