diff options
| author | Adam Soltys <[email protected]> | 2026-11-07 22:34:18 -0700 |
|---|---|---|
| committer | Adam Soltys <[email protected]> | 2026-11-07 22:34:18 -0700 |
| commit | d6b9298e2dfde43542a516b3b0cac4770592a794 (patch) | |
| tree | 047d5ec76ea1e659fa186f043f632a4f18a6ea7f /tools/sensitive-feed-test.js | |
| parent | a1cb2db1907313530b50798dea0e37278cbbb0ef (diff) | |
| download | coinosv3-d6b9298e2dfde43542a516b3b0cac4770592a794.tar.gz coinosv3-d6b9298e2dfde43542a516b3b0cac4770592a794.zip | |
A scanned LNURL opens as what it is even while Spending is still connecting. "I refreshed and scanned it again and it put the lnurl in the recipient field and gave me a zap button" (Adam, 2026-11-08): zaps' matchSendText turned everything down until canLnPay, which is false for the first moments after a refresh, so his own withdraw link fell through to the send form's "Zap LNURL…" affordance. A withdraw pays us and needs nothing spendable, and only the GET says which kind an lnurl is, so a scanned or pasted lnurl is taken first and resolved; a pay one meets the pay checks where it's paid. lnurl-withdraw-test covers the scan with nothing spendableHEADmaster
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VMan6Ts5Tktega8VbLg31q
Diffstat (limited to 'tools/sensitive-feed-test.js')
0 files changed, 0 insertions, 0 deletions