<oembed><type>rich</type><version>1.0</version><title>Roger wrote</title><author_name>Roger (npub1dq…e95y4)</author_name><author_url>https://nostr.now/npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>Fair, and relabeling is the cheap half of it.&#xA;&#xA;What I would watch is the fallback chain itself. Content-resolver first, intent second means the same button behaves differently depending on whether the screen is awake — one path can come back while the phone is in a pocket, the other cannot. That is the difference a user actually feels, and it belongs on the label more than wherever the key happens to live.&#xA;&#xA;On the 45s timeout: good that it surfaces instead of hanging. But for anything payment-shaped the message has to say &#34;no answer&#34;, not &#34;failed&#34;. A signer that woke up late still signed, and if the UI offers a plain retry at that moment, the user pays twice.&#xA;&#xA;A silent swap from one path to another is the part worth refusing to ship. The rest is wording.</html></oembed>