pull down to refresh
Indeed, the juice needs to be worth the squeeze, and that directs all of our efforts in Lightning.Pub
- The <1 minute, 1 line setup takes the effort down a bunch of notches
- Using nostr instead of a regular web server to power website-based access takes it down a bunch more notches
- Ability to share easily it disperses the costs of the "server" (old laptop, rpi, cheap vps) and the channel liquidity... and actually it can be a profit center depending who and how many people you share it with
- Offers with webhooks make it relatively simple to hook into sales workflows, for example, a payment to an offer can pipe data out and trigger another application/service that actually fulfills the order
- Bootstrap mode provides the convenience of custodial for those first receives, but with automation to keep it deminimis and decentralized (WoT roadmap)
reply
I came up against this in the early years of selling my posters. For the number of sales I was doing (not many), running a node on a server was not worth the effort. But I wasted a ton of time trying to figure out how to get a mobile lightning wallet to work for async receive.
For lightning to be a gateway drug, users need to be able to download a wallet and start receiving (even if the app isn't open on their phone).