Unfortunately doesn't work for both self-custodial NWC app and Alby hosted NWC
It's meant to work. We probably have a bug.
What errors are you getting in your console?
reply
3234 sats \ 8 replies \ @saunter 13 Feb
Uncaught (in promise) EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'".
at bakeCollection (content.7f229555.js:2064:98610) at Object.u (content.7f229555.js:2064:93234) at Object.g [as call] (content.7f229555.js:2064:93437) at es.o [as emit] (content.7f229555.js:2064:85238) at es.stop (content.7f229555.js:17:30157) at es.eoseReceived (content.7f229555.js:17:31755) at content.7f229555.js:17:8787 at Array.forEach (<anonymous>) at T.eoseReceived (content.7f229555.js:17:8754) at content.7f229555.js:17:11970
reply
@ekzyis looks like the nostr library violates CSP
reply
0 sats \ 6 replies \ @ek 13 Feb
Mhh, interesting, I tested NWC when we launched and I could generate NWC requests 🤔
reply
I think it might be that the library uses wasm, some browsers probably don't support it, and we allow unsafe-eval-wasm but not unsafe-eval
reply
Oh, you'll have issues with graphene's browser and people running lockdown mode on iOS.
That's pretty crap that it's pulling in web assembly for whatever reason. There's really no need.
reply
0 sats \ 3 replies \ @ek 13 Feb
Ah. @saunter, which browser are you using?
reply
Arc
reply
Hmm I used it on arc without a problem.