pull down to refresh
0 sats \ 7 replies \ @k00b 12 Aug 2023 \ parent \ on: New features of magic webstore: store metadata, nostr auth, notifications & more bitcoin
I believe you'd recreate the issue by creating multiple concurrent LNC connections with the same pairing phrase. You created multiple serially.
I can't imagine a scenario where I would want to do that. Why can't Bob/Carol just pay Alice by triggering an invoice through Alice's store? There is no scenario where Bob or Carol would need to connect to Alice's store.
reply
through Alice's store
If Alice's store doesn't have a server to generate an invoice, there's nothing to go "through."
The magic of magic webstore is that Alice isn't hosting the store. Magic webstore is a statically served html file that pulls store-specific data from nostr and which store you're viewing is specified in http GET params.
LNC connections need to happen client side or Alice would need to run yet-another-service.
reply
Seems like Alby would be the best way to go about it then. LNC requires a client/server relationship. Alby is a pretty nice go between for services and nodes(via LNC) though.
reply
Adding a form to connect to Alby (and, through Alby, maybe even to your own node) is a good idea. Nonetheless, I would still like to reduce the number of dependencies by supporting a connection string directly to your own node.
reply
So Alice would sign up for Alby with their LNC pair phrase and Bob and Carol would request invoices through Alby?
reply
I guess so? I still don't really get why Bob/Carol can't just pay Alice through invoice generated through Alice's LNC connection into some database on magicwebstore's backend, BUT...You would have to look at the alby dev docs. It seems backwards than how it is commonly used, which as a payer tool, not a payee tool, but it could be both maybe. As you know Lnbits is kind of the go-to for webhook stuff though. I personally would use BTCPay on Alice's end but regardless I like the project and I like the vision and hope you find the solution you need!
reply
"some database on magicwebstore's backend'
Magic webstore has no backend
reply