Repository navigation
v1.4.3
Pre-releaseHeld, not shipped. This build was never published to Zapstore. Comments
work, but nothing tells you a comment arrived — no mark on the task, no
notification — so the feature is not finished as an experience. The comment
UX (unread marks, a place to catch up, deterministic clearing) is being
designed and will ship as 1.5.0. See
#218 and
#219. The APK below is a
valid signed build if you want it; it is simply not the release.
Task comments are here
Every task now has a COMMENTS thread. On a shared list it is a conversation with the people you share the list with; on your own tasks it is a notes field that syncs across your devices.
Coming from Zapstore? The listing is still on 1.4.0, so comments are brand new to you, along with everything else from v1.4.1 and v1.4.2. v1.4.2 was withdrawn and never published; everything in it is here.
Added
-
Comments on tasks. Write a comment, long-press your own to edit or delete it, with an "edited" marker and the author's display name next to their npub. Works in secret-key mode and with Amber. Each comment is a separate NIP-44-encrypted addressable event (
kind:35002) signed by the list's group key or by your own key, and carries no tag referencing the task, so relays cannot see which task a comment belongs to, or how many comments a task has. Deleting a comment republishes an empty tombstone, which replaces the text on the relays. Logging out erases the local comment store. (#157, #159, #160, #161, #163, #164, #165)Comments were built in the 1.4.1 and 1.4.2 trees. Neither was published to Zapstore, so 1.4.3 is the release that actually brings them to you.
Also new since 1.4.0
- Task-loss protection for synced lists. Publishing waits for at least one successful relay fetch in the session, refuses to publish a list that shrank below half of its last relay-confirmed size unless you run a manual sync, and keeps a change queued rather than reporting success when a send reaches no relay. (1.4.1)
- Emptying a list reaches your other devices. Deleting the last task in a list was never sent, so the task stayed on every other device. (1.4.2, #182)
- Tasks are no longer deleted because a sync was incomplete. An interrupted or partial fetch used to remove real tasks. A list that did not arrive at all is now left alone. (1.4.2, #182)
- Your relay settings are used at startup. A cold start fell back to the built-in public relays even though your own relay was saved, then overwrote your settings with the list it read from those public relays. This is why data could look missing after a reinstall: the app was asking the wrong relays. (1.4.2, #197)
- Settings screens are readable in dark mode, Secret Key Management is fully translated, and a missing translation now fails the build instead of silently falling back to English. (1.4.2, #183, #189)
Fixed
-
Comments reach the relays even after a brief network problem. This is the headline fix of this release. When the app reconnected to a relay it closed the old connection and immediately opened a new one. The library underneath treats that as a shutdown, so the relay stayed dead for the rest of the session. Anything written afterwards, comments in particular, was accepted by the screen, reached no relay at all, and was gone on the next start. The reconnect now waits for the connection to actually come back, and reports how many relays it reached. (#188, #214)
-
A comment that reaches no relay is retried instead of being dropped. Sends that fail are queued on the device and flushed on the next connection, so a comment written while offline survives. The queue is erased on logout. (#201, #212)
-
Sending reconnects first when the connection is known to be down, rate-limited so that flushing a backlog of queued messages pays for one reconnect rather than one per message. (#215)
Changed
-
The relay status row says what actually happened. Tapping reconnect used to look identical whether every relay came back, none of them did, or nothing was attempted: a spinner, then the same red badge. It now reports how many relays reconnected, says so plainly when none could be reached, and stays silent when there was nothing to do. (#215)
-
The Notifications settings entry no longer appears. It was unfinished UI with no service behind it, so its switches did nothing while claiming otherwise. It returns together with the notification service. (#201, #210)
Known issues
- Comment notifications are still not delivered while the app is closed. The settings entry that implied otherwise is gone from this build rather than being made to work. (#201)
- When the background notification service does arrive, it will connect to the public default relays regardless of your relay settings. (#198)
- Publishing your relay list writes an intermediate version to the relays you are removing, and those relays keep it. (#193)
- Seven other places in the app still publish without checking that a relay accepted the event. They are the same shape as the comment bug fixed here; the most consequential is adding a task to a shared list. (#213)
Verifying this build
The APK here is 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>. That fingerprint was confirmed against the published v1.4.1 production APK, re-downloaded from this repository, not just against a local note. The tag v1.4.3 is a signed tag on the merge commit 83eacb3c.
meiso-v1.4.3-production.apk sha256 2d42f9dd7960a30042354d7d3c6ea5d3c23f0d195379c14683843d1362482aa4
No beta APK is attached to this release, deliberately. Zapstore's publishing tool picks one APK from the latest GitHub release, and with both flavours attached it picks the beta one, which carries a different package id (jp.godzhigella.meiso.beta) than the listed app. Measured on this release: two assets resolve to the beta package, the production asset alone resolves to jp.godzhigella.meiso. The beta build remains available as the 30-day workflow artifact on the Build APK run for this tag.