Repository navigation
v1.4.2
Pre-releaseComments on tasks, task-loss protection, relay-settings integrity and a translated settings screen.
Coming from Zapstore? The Zapstore listing is still on 1.4.0, so this update also brings you everything from v1.4.1 — the task comments described below, the task-loss protection for synced lists, shared-v1 collaborative lists and the optional Tor/SOCKS5 proxy in the CLI, and the corrected collaborative-lists encryption documentation.
Added
-
Comments on tasks. Open a task and there is now a COMMENTS thread below SUBTASKS. Write a comment, long-press your own to edit or delete it; an edited comment is marked as such, and each one is labelled with its author's display name next to their npub. On a shared list it is a conversation with the people you share the list with — their comments appear as they are written. On your own tasks it is a notes field that syncs across your devices. Works both in secret-key mode and with Amber. (#157, #159, #160, #161, #163, #164, #165)
Comments are encrypted the way your tasks are: one NIP-44-encrypted addressable event per comment (
kind:35002), signed by the shared list's group key or by your own key, with the body capped at 2000 characters. The event carries no reference to the task it belongs to — the task association lives inside the encrypted payload, so a relay cannot see which task a comment belongs to or how many comments a task has. Editing republishes the same comment; deleting republishes an empty tombstone, which replaces the text on the relays rather than leaving it there. Logging out erases the local comment store.These landed in the 1.4.1 tree but were left out of the 1.4.1 release notes. 1.4.1 was never published to Zapstore, so for most people this is the build that introduces them.
Fixed
-
Deleting the last task in a list now reaches your other devices. Emptying a list was never sent: the sync built its list of changes from the tasks that still existed, so a list that had just become empty had nothing to send. Going from three tasks to one synced correctly; going from one to zero did not, in both Amber and secret-key mode, and the last task stayed on every other device. (#182)
-
Tasks are no longer deleted because a sync was incomplete. A task missing from a fetched list is now treated as deleted only when that list's own published timestamp is newer than your local edit. Previously anything absent and older than a day was removed, so an interrupted or partial fetch deleted real tasks. A list that did not arrive at all is left alone. (#182)
-
A device that holds an older copy of a list now gets the newer one. When a sync found the relay holding an outdated list, the re-publish was skipped as "unchanged since last publish" and the pending flag was cleared anyway, so the relay never caught up until the list changed again for an unrelated reason. (#182)
-
Amber mode no longer misses lists during a full sync. The fetch ignored events the live subscription had already seen, so a full sync could come back without lists that plainly existed — and the missing lists were then treated as "nothing to compare against". (#182)
-
Your relay settings are used at startup. When the app started it initialised its connection from an in-memory list that is empty on a cold start, and fell back to the built-in public relays even though your own relay was saved. It then read the relay list published under your key from those public relays and overwrote your settings with it. Reinstalling the app was the easiest way to trigger this, which is why data could look missing afterwards: the app was asking the wrong relays. (#197)
-
A relay list is only replaced when it was actually read. The settings sync now distinguishes "no relay could be reached" and "no list published" from "your list was read", and keeps your saved settings in the first two cases. (#197)
-
A list named "Default" no longer puts other tasks at risk. Such a list shared an internal key with the built-in default list, so tasks in one could be judged against the other's timestamp. (#182)
-
Settings screens are readable in dark mode. Secret Key Management, Relay Server Management and Cryptography Details used fixed light-mode colours that did not follow the theme. (#183)
Changed
-
The settings screen is tidier. The Amber-mode and auto-sync explanations have moved from the top-level settings list into the screens they describe. (#183)
-
Secret Key Management is translated. Every user-facing string on the screen was hard-coded in Japanese and now follows the selected language, in English, Japanese and Spanish. A missing translation now fails the build rather than silently falling back to English. (#189)
Known issues
- Comment notifications are not switched on yet. Settings → Notifications shows two switches and remembers them, but this build never starts the background service behind them, so nothing is delivered while the app is closed — despite what that settings row says. Comments themselves are unaffected: they arrive over the normal connection as soon as the app is open. (#201)
- When that background service is switched on, it will connect to the public default relays regardless of your relay settings. The startup fix above covers the app while it is open; the background task cannot read your relay list yet. (#198)
- Publishing your relay list writes an intermediate version to the relays you are removing, and those relays keep it. (#193)
- The relay connection goes stale after a few minutes; a manual reconnect is still needed. (#188)
Verifying this build
Both APKs here are signed with the certificate that every production release has used, including the 1.4.0 build currently served by Zapstore:
Signer certificate SHA-256: ba94cf068f152770bb90111e3ced0a365c3d8bea6434f49bc78a2989947c633c
Check your download with apksigner verify --print-certs -v <apk>. The tag v1.4.2 is a signed tag on the merge commit 016c91d7.
Beta flavour only: the app-beta-release.apk attached to earlier releases was built in CI and signed with a throwaway certificate that differed from release to release, so it could never be installed over a previous beta. This asset is a local build carrying the certificate above. If you have an older jp.godzhigella.meiso.beta installed, uninstall it before installing this one; from here on beta updates will install over each other. The production APK is unaffected and was never built in CI.