I don't like Zaps.
It's a rushed solution. The whole benefit of lnurl style solution on #nostr is you don't need to run dns to be self-sovereign, all you would need is an npub for the requesting ping pong.
This is better:
I don't like Zaps.
It's a rushed solution. The whole benefit of lnurl style solution on #nostr is you don't need to run dns to be self-sovereign, all you would need is an npub for the requesting ping pong.
This is better:
Iβm always ready to evolve to the next best thing
You could still return a sever based lnurl with the native nostr solution, but you could also do in a completely clientside way
Zapped!
now we're talking. one good idea after another. nostr is an incredible accelerant for innovation in digital sovereignty
#[0]
this deserves more traction
Zaps arent needed anyway. All we have to do is message anyone on nostr our lightning addressβοΈ
Unfortunately, that isn't a user friendly approach to Bitcoin. If a person automatically has access to zap someone constantly presented to them, as opposed to needing to go through even one or two more steps, it makes a huge difference in engagement. Think of the difference between buying on Amazon with a single click, or having to go through a belabored process to make a purchase. People largely want their transaction to be simple, convenient, and easy.
When will you implement it?
That's likely going to be an unpopular take here Ben. But most of us plebs are depending on you dev types to get us there safely. Make it better.
π
Serverless LNURL? Sounds huge!
#[0]
Ugh I hate me right now, meant to paste this #[4]
Bolt12 over nostr > LNURL over nostr > LNURL over HTTPS
#[2]
I donβt fully understand what you said but Iβm alway interested in better implementations.
Until someone comes up with a better method, Iβll happily keep zapping good contentβ‘οΈπ
Thank you all devs!