Tags give the ability to mark specific points in history as being important
-
v0.1.13
protectedRelease: staircase v0.1.13cf7a7cca · ·Staircase 0.1.13 — the chat's connection status is a small indicator in the top bar (a green dot when connected; soft Connecting / Syncing / Reconnecting; Offline only after 30 s) instead of a red strip, with plain-language details on tap. Messages sent while offline wait and go out by themselves once the chat reconnects. Desktop: one themed message menu with Copy selection / Select all text. Multi-device catch-up fetches missed messages while reading the other device's documents and brings 8 groups up to date at once.
-
v0.1.12
protectedRelease: staircase v0.1.127370dd51 · ·Staircase 0.1.12 — without multi-device, a device that falls behind a group (cannot open its newest messages) no longer changes it or sends into it: it refuses approvals, invites and renames, holds sends after a run of unreadable messages, and says so, instead of splitting the group. Messages are selectable (part or all, with Reply / Copy message in the text menu), links open, Copy image; a profile screen (npub, nprofile, QR, verified NIP-05) and editing your own profile; coordinator invites by QR and one link parser for every cordn-web link; linked devices share the Blossom list on the newest tip.
-
v0.1.11
protectedRelease: staircase v0.1.11379ccb46 · ·Staircase 0.1.11 — multi-device: ignores a tip older than one already seen (a relay that missed a publish could hand over the previous tip, and it was applied as new); every tip is dated after the newest seen. Settings › Multi-device shows where the last publish landed (relays, Blossom servers), with Check, Repair, Retry/Republish and an activity log; Settings › About shows the app version.
-
v0.1.10
protectedRelease: staircase v0.1.1072804505 · ·Staircase 0.1.10 — share: photos and videos shared from another app now go out stripped (0.1.9 sent the untouched bytes while the screen said metadata removed; Send captured the pre-strip list). Verified on Pixel 6 Pro and 8a: sent photo re-encoded, upright, no EXIF; video re-muxed without location/comment; three photos back to back with no ANR
-
v0.1.9
protectedRelease: staircase v0.1.9e36eb63d · ·Staircase 0.1.9 — media: metadata (location, camera, time) stripped from photos and videos before sending (RelayTools' sanitizer; MP4/MOV re-muxed on Android), photo sends no longer freeze the app (encrypt/hash/decode off the main thread); android: share target for photos, videos, files and text; ui: group pictures (upload, URL or emoji), a stuck group shows an orange dot; contextvm: large replies reassembled in order and digest-checked (out-of-order chunks silently corrupted fetched messages), calls take the reply without waiting out slower relays; includes the unpublished 0.1.8
-
v0.1.8
protected7d73831d · ·Staircase 0.1.8 — streams: a msg_sub_many the coordinator never starts (request on a relay it was not reading) fails after 30 s and retries, and a chat reads live only once the stream started (it stayed "live" with nothing arriving until restart); sync: a parked group holds sends and commits until it reads again (a parked desktop sent messages nobody could read), a skip is checked against the next message (undone if that one is unreadable too, sends held until confirmed if nothing follows), a parked group whose cursor moved past clears; ui: stuck-chat banner with Skip it / Details, selectable connection details, member actions in a menu, Tab completes a mention; zapstore listing and changelog
-
v0.1.7
protectedRelease: staircase v0.1.70195793c · ·Staircase 0.1.7 — relays: a relay dropped for a publish timeout or a hung connect reconnects (it stayed dead until restart), subscriptions a relay ended are re-opened, a publish returns on the first accept; contextvm: replies matched by e tag first and rpc ids atomic (a kp_list reply could land on msg_fetch_many); logging: INFO by default in release with a Verbose toggle in Settings, no payloads or full identifiers above debug, repeating lines logged once
-
v0.1.6
protectedRelease: staircase v0.1.602c16b22 · ·Staircase 0.1.6 — multi-device: a ratchet repair only for a collision on our own leaf (another member's duplicate generations no longer make every device commit), inbox: invites sealed to another device's key package stay out, an already-used invite can't roll a group back, Dismiss on invites; Quartz re-vendored at aefbcd0b2a (upstreamed patches 1, 2, 3, 9, 10, 11, 12)
-
v0.1.5
protectedRelease: staircase v0.1.53232c881 · ·Staircase 0.1.5 — MLS interop: adds record unmerged leaves (RFC 9420 §7.7) instead of blanking the path, so ts-mls adds into long-lived groups no longer fork staircase members off (and staircase adds are accepted by ts-mls); multi-device meta ping-pong with cordn-web stopped; join requests another admin handled leave the inbox
-
v0.1.4
protectedRelease: staircase v0.1.4503039dc · ·Staircase 0.1.4 — multi-device safety: a device behind a skipped sibling commit holds its sends and refuses commits until it converges; tip publishes re-check the tip before sending (no overwrite from an older read); group documents that no longer open with the current key are replaced; ratchet repair waits, re-checks and shows itself; Group info shows the group id and Sync details
-
v0.1.3
protectedRelease: staircase v0.1.3e2a7b3b9 · ·Staircase 0.1.3 — sync reliability: ambiguous sends are reported as such (not failed), no automatic skip past unreadable messages (explicit user action in the connection dialog), lost messages made visible; 'Send while behind' removed; CI desktop packaging serialized
-
v0.1.2
protectedRelease: staircase v0.1.27138bab0 · ·Staircase 0.1.2 — multi-device convergence (epoch fingerprints, lineage, publish retry, parked recovery, behind guard), desktop logs and sync diagnostics, mentions, former-epoch decrypt, relay/sync scaling, Blossom server setting