nostr:npub12gyrpse550melzx2ey69srfxlyd8svkxkg0mjcjkjr4zakqm2cnqwa3jj5 says its fixed ?
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s are you guys going to fix this ?
Discussion
I deleted/recreated the nwc and zapped the last 2 replies of yours. I see nothing in mutiny. it’s been >5mins. damus v1.7 testflight
If youre using mutiny on ios you have to open the app for that zap to go through, it can’t be in the background.
Whats the point of nwc then ?
Is there any change between AppStore and TestFlight versions that might affect mutiny?
yes but no it won’t affect mutiny
You can zap several notes and then open mutiny afterwards. It’s a non custodial nwc solution? Mutiny can be used on a browser and that might be better for nwc. But don’t let me speak for them, I could be 100% wrong on all of the above. nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg
Correct.
Definitely makes sense, but seems pretty advanced for most users
Opening an app is too hard? For who?
I was talking about the mode where you have it running on your desktop + nwc, you don’t need nwc to open up the app.
Also, expecting users to know to open up the app when using nwc is too hard, yes.
Well they have to open the app to use it in the first place, so not worried about it. Thanks for the feedback though, looking forward to NWC being fixed in damus.