pull down to refresh

2255 sats \ 6 replies \ @sudocarlos 14 Feb \ parent \ on: SN release: NWC & LNBits for sending, LND for autowithdraw, NSFW labels, & more meta
iOS 17.3.1 - Safari (PWA). Not sure if my string is good: nostr+walletconnect://<long-alphanumeric-string>?relay=wss://relay.getalby.com/v1&secret=<secretstring>
write
preview
42 sats \ 5 replies \ @k00b OP 14 Feb
The string might be bad. We don't validate it to check. I'll run some more tests in all the problem browsers tomorrow and see if I can fix it.
reply
987 sats \ 4 replies \ @ek 14 Feb
Going to add the validation tomorrow.
However, there should be a toast with some error message if the credentials are no good1:
https://m.stacker.news/16088
The form also shouldn't close if the info event wasn't found. And if it was found, the wallet indicator should turn green.
But maybe the error is CSP + browser combination again which throws an error at a location which isn't toasted.

Footnotes

  1. That check only verifies everything up to but not including the secret since a correct secret is not required to receive the info event unfortunately. ↩
reply
0 sats \ 3 replies \ @sudocarlos 14 Feb
CSP?
reply
42 sats \ 2 replies \ @ek 14 Feb
Oh, sorry, I mean Content Security Policy. This is supposed to tell your browser what code is good to run and which should get blocked. It might be blocking too much depending on the browser.
reply
0 sats \ 1 reply \ @sudocarlos 14 Feb
Gotcha. Also, shouldn't it say "detach" instead of "unattach"? It's your app, but feels more natural
reply
42 sats \ 0 replies \ @k00b OP 14 Feb
lol yes @ekzyis speaks better English than I do
reply