Skip to content

0.2.1

Choose a tag to compare

View all tags
@cruelacid cruelacid released this 25 Sep 22:31
· 3 commits to main since this release
0.2.1
80b0fe4

Nectenda 0.2.1

Added

  • Presence — collaborators' names, colours and cursor positions — is now end-to-end encrypted. Until now it travelled in the clear, so the server could see where in a note each person was working; it no longer can.
  • Collaborators' mouse pointers now show in the note you share, labelled with their name. When someone is off-screen, an indicator at the edge of the view points to them and to their cursor. Two new settings let you stop sharing yours, or hide theirs.
  • Every note in a shared folder now shows whether the server has all of your changes: a Nectenda icon at the top right of the note, carrying connection state, a count of who else is there and quick settings; marks in the file explorer; and a sync-state inspector that compares the note on disk with the synced document. This replaces the status bar item, which is gone — Obsidian on a phone has no status bar, so the status now lives where a phone can show it.
  • Command-palette commands, a ribbon icon, and right-click actions on folders for sharing and managing members.
  • A warning when a note in a shared folder is too large to sync, when it arrives rather than after you have typed into it, and a list of such notes in settings.
  • The plugin's repository now carries a CHANGELOG.md, and each GitHub release lists what changed in that version.

Fixed

  • An edit could be lost permanently. If a change was sent in the moment a folder was still catching up, the plugin could record a sync position that skipped it, save that position, and never ask for the change again — so it was gone, with no warning and nothing to restore from. This is the most serious fix in this release, and it affects every version up to 0.1.5.
  • Two vaults opening the same not-yet-synced note could duplicate every note in the folder. Both vaults filled the note from disk independently, and the two copies were combined rather than recognised as the same text. Both devices then agreed on the doubled version. Most likely with the server unreachable, and possible without it.
  • Changes the server silently dropped are now sent again after a reconnect, and are no longer lost if Obsidian is restarted before they are confirmed.
  • Notes up to 16 MiB now sync, raised from 4 MiB. A change too large to send now shows an error on the note instead of retrying in a loop.
  • A note another member created just as you joined a shared folder could silently never reach your vault.

Known

  • Collaborators still on 0.1.5 or earlier will appear to have no cursor. Their presence is sent in the clear, and this version refuses to read that rather than accept something the server could have written. Their edits still sync normally — only their cursor, name and colour are missing, until they update.
  • iOS is untested on a device. It should work — it is the same JavaScript as Android — but nobody has run it on an iPhone, so it is not claimed.
  • On Android, all vaults in the app share one secret store: signing one vault in signs them all in.
  • There is no read-only membership. Everyone in a shared folder can edit it.
  • Not audited. The client ships unminified and the build is reproducible, so the claim is checkable — but no third party has checked it.

0.2.0 was published on 25 September 2026 and withdrawn before the community
directory listed it: its automated review rejected the release over how one
animation was applied in the code, not over anything the plugin does. Nobody
was ever offered it, so its contents are listed here as 0.2.1 rather than as
a version of their own. The 0.2.0 tag and its release still exist, and this
is the note that explains them.

Installing

Install main.js, manifest.json and styles.css into
.obsidian/plugins/nectenda/.

Verifying this build

The bundle is not minified. The code that encrypts your notes is the code
you can read, and you can confirm this release was built from this source:

sha256(main.js) = 8022aca97cb96e56c5993d1312a45db0993ee788fc3de4c516f2f28c86a8acf3

git clone <this repo> && cd nectenda-plugin && git checkout 0.2.1
pnpm install --frozen-lockfile && pnpm build
shasum -a 256 packages/plugin/main.js

The toolchain is part of the answer: packageManager in package.json
pins the pnpm version, and the recipe above uses it. A different package
manager produces a byte-different bundle with identical behaviour, because
esbuild records each module’s resolved path in a comment.

Built from e45490f.

Assets 5
Loading