i just zapped nostr:npub1ne99yarta29qxnsp0ssp6cpnnqmtwl8cvklenfcsg2fantuvf0zqmpxjxk 5 sats AFTER successfully generating an invoice and copy-pasting it on nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm like a #normie 
NOW , today, i need to learn how to skip all that normie activity, and open the extension automatically to carry on with the zapping. #zap #pow #progress #rosecoco
bet they didnt see this value for self we are creating it was too far down the time line. nostr:npub1nqx3lfjxpkqhck3kgrdtkhncvffe94l7qrep6ftw49nphnmw9szqvh3quf
hahaha my own zap button you cant even make this shit with AI yet, GPT is yet to be fed nostr tools & development kits.
makes you wonder, who is actually, pretending to code up in this bitch? huh????
nostr:note1tk3de8yhwhdfq2zwzkh9skqz2fr5m23ywpl6748v7mazktetghtspjecyd
generally most nostr clients generate custom URIs that start with "lightning:" when discovering things like invoices or LNURLs to communicate with other apps. I was under the impression that Alby responds to lightning: URIs so clicking on links should open the extension already.
If the client you are using doesn't generate lightning: URIs then copy-pasting invoices is probably the way out (this was the norm before 11/22). generally when protocols used in links can't be handled by the browser it gets passed to the OS to find an application to handle the link. A way you can do this is create a entry for xdg-open to respond to lightning: URIs and set whatever command needed to execute.
Alby should respond and interact with the lightning i am supposed to create a zap event next that collects the URI you say to open alby then proceed with the zap once i call the function on the application . this is build to test the uri is being generated correctly for each address.
i shall also look into creating an xdg-open
perhaps you'll find this helpful. Sounds like your build requests invoices correctly if successful payments are already registered as zaps.
You only need to add lightning URIs in order to open wallet apps then -- your client just waits for the event 9735 to show up that says the payment was completed (I imagine you want your client to handle the zapper and zapped user differently).
Pretty much yes. i have made an event 9734 for the zap requests thats already interacting with alby. the payment was next, 9735 . i love this illustration. thank you so much.
please consider testing your zaps on nostr:npub1e4qg56wvd3ehegd8dm7rlgj8cm998myq0ah8e9t5zeqkg7t7s93q750p76 😎
your feed....😳 🫣 I thought you were religious
i shall test some zaps of course. i'm sure they shall pop up somewhere on the client 😉 and i always advice most not to scroll my feed. my mind tends to wander across all forms of existence.. i read religion literature for education and knowledge purposes.
