Nostr View

5be64 - 2y

We might actually be able to get nostr wallet connect working with our non custodial mobile wallet afterall. It won't be perfect but makes Mutiny nostr zap integrations easier than asking nostr clients to import our node directly. This should allow for frictionless non custodial zapping without needing an always online node, custodian, or server. #showerthoughts

undefined
undefined
undefined

5be64 - 2y

Cc nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5

undefined
undefined
undefined

5be64 - 2y

We still need to review the spec and see what it looks like in Damus. But looking at Amethyst, I like that it is a form that users can put in all the parameters manually. Not sure if Damus is allowing that or just using the URL connect option. It could be error prone* to be able to do the URL based connect flow but will have to look at it. It may seem like it would be a natural fit with us being browser based, but it depends on if the user installed our app as a PWA (segregated storage) and if Damus is opening up the link in safari or in app web browser.

undefined
undefined
undefined

jb55 @jb55 - 2y

Damus prefers to scan a qrcode but it also handles nostrwalletconnect links

undefined
undefined
undefined

5be64 - 2y

Thanks for the information. Yeah QR scan may be difficult since it'll commonly be a PWA on the same phone. And URL links could work but there's edge cases and won't work well if the user installed as a PWA. A manual form as a fallback would solve those problems but we'll have to implement this first so TBD on that.

undefined
undefined
undefined

8c3b2 - 2y

For the spec better look at the "official" nip repo, the getalby repo might be out of date

undefined
undefined
undefined

semisol @semisol - 2y

Extremely

undefined
undefined
undefined

5be64 - 2y

Will do!

undefined
undefined
undefined

bumi @bumi - 2y

this is for sure is possible. I experimented with it before, but the app needed to be running to be connected to the relay. let’s chat, I’d be happy to brainstorm and help

undefined
undefined
undefined

5be64 - 2y

In some cases on android as a PWA it'll stay backgrounded and active from my experience so far. Otherwise, would they just all be queued up? Since it is nostr based then it is async by nature, so would it be fine if all the zaps just get queued until the user opens their app again?

undefined
undefined
undefined

bumi @bumi - 2y

yep. theoretically also a push notification could be sent to the user to open the app.

undefined
undefined
undefined

8c3b2 - 2y

Yup

undefined
undefined
undefined

5be64 - 2y

In some cases I think you can trigger some actions on push notification too. So might be possible to send transactions simply from push notification. I think this is how Phoenix does receives via push notification on iOS. And PWAs on iOS now get access to the same app notification experience apparently.

undefined
undefined
undefined
Showing page 1 of 1 pages