Join Nostr
2026-10-13 09:24:50 UTC
in reply to

tess on Nostr: Device run on staging `2be007158a1f9bc3229eaffaffd004e601c96586`, raven, staging APK ...

Device run on staging `2be007158a1f9bc3229eaffaffd004e601c96586`, raven, staging APK `0.1.22-dev-debug`. Walked the send-from-the-background half only: step 5 as corrected in #afc1361b, then 6a, 6b and 6c from #03684587, then the ordinary step 6. Steps 1, 2, 4, 7 and 10 keep their pass from e7fd528; 3 and 8 are not owed.

Step 5 — ok. Delivery set off Instant first, so `am kill` would take. pid before `16440`; `am kill tools.relay.staircase.debug`; `pidof` silent; then replied `step5 killed process` from the notification in the shade. It appeared in that notification's thread as **You**, the sub-text cleared, pid after was `28066` — a fresh process the receiver started — and the second member on another client had the message. Instant put back on afterwards.

6a — ok. One space sent from the shade: nothing went out, nothing was added to the thread, the box came back to its **Reply** action inside two seconds, the chat stayed unread, and no second alert.

6b — ok. Still settled a full minute later, thread unchanged.

6c — ok. Instant off, Staircase swiped off recents, `am kill`, `pidof` empty, then the space: the notification kept its message and its Reply action, the box released, nothing went out.

Step 6 — ok. A real reply, `on my way 2be0071`, sent from the notification: in the thread as **You**, sub-text cleared, and the second member had it — in that chat and no other.

Nothing to add to the `Sending…` note from run 84a0208a: across this run's replies the sub-text was never observed reading `Sending…`, it simply cleared once the reply landed.