You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Verified still open against current source (build 102, 2026-08-10). NIP-44 v3 itself is fully shipped — these are UX follow-ups discovered during that rollout.
A single user action can surface multiple approval prompts with no bundled "always allow." e.g. Spectr's deck-sync fires nip44v3_encrypt then sign_event as two separate prompts for one conceptual action, and the foreground alert has no always-allow affordance for either step (only the detail-view path does). Clave/Views/MainTabView.swift:77-128 root .alert() still only has Approve/Deny/Not-now. Cheapest fix: add a "tap for options" path from the popup into the detail view that already has the toggle.
Bunker pairing completes with no confirmation shown to the user.nostrconnect:// pairing shows an explicit account-pick → permissions → confirm flow; bunker:// pairing (client-initiated, often arrives via APNs while the app is backgrounded) auto-accepts silently on a valid secret. Client-metadata (name/icon) now flows through the connect RPC (feat(nip46): accept optional client metadata in bunker connect request #75, shipped), so a post-pair confirmation toast/notification is worth adding now that there's something real to show. Shared/LightSigner.swift (connect auto-accept).
Verified still open against current source (build 102, 2026-08-10). NIP-44 v3 itself is fully shipped — these are UX follow-ups discovered during that rollout.
nip44v3_encryptthensign_eventas two separate prompts for one conceptual action, and the foreground alert has no always-allow affordance for either step (only the detail-view path does).Clave/Views/MainTabView.swift:77-128root.alert()still only has Approve/Deny/Not-now. Cheapest fix: add a "tap for options" path from the popup into the detail view that already has the toggle.nostrconnect://pairing shows an explicit account-pick → permissions → confirm flow;bunker://pairing (client-initiated, often arrives via APNs while the app is backgrounded) auto-accepts silently on a valid secret. Client-metadata (name/icon) now flows through the connect RPC (feat(nip46): accept optional client metadata in bunker connect request #75, shipped), so a post-pair confirmation toast/notification is worth adding now that there's something real to show.Shared/LightSigner.swift(connect auto-accept).Source: internal backlog triage, 2026-08-10.