Oddbean

Current zPay.live shareable paywall URL takes 2-3 sec to open & 1-2 sec to generate a payment invoice, which isn’t too bad. For U.S. users, it's slightly faster. New version, however, takes mere milliseconds for both processes 🤌, low latency worldwide 🕊️ using concurrency & edge functions. After further testing & polishing, it’ll be live. https://video.nostr.build/3367082670ee501bad830eb398e3cf0bc2632187a2ac44d26f068696be4de591.mp4

It doesn’t use a centralized database. The content URL is encrypted, packaged within the URL, & cryptographically signed to ensure integrity (preventing tampering of price and wallet address). When you click on the URL, it performs calculations, compares the hash & verifies the URL. Once verified, it initiates the invoice creation, which now runs concurrently and can be canceled later if needed. Wallet providers have their own limitations. Lambda serverless functions can scale up to millions of requests per second, but they have a warm-up time and noticeable latency, especially for users far from a data center. The new implementation uses Edge functions distributed worldwide, which is the best possible option currently. The short URL is simply a lightweight edge proxy with caching, and in the browser's address bar, you’ll see the original URL. Comparison https://image.nostr.build/8801968c747c59364fe05bf597b494bad6c174abd4475b6b98c1d714b5be0fd5.jpg

Is it technically possible / relatively simple to enable some kind of a notification / message to be received by the link creator with each payment? As I’m using the same Lightning address for all paywalled links (and zaps and other Lightning payments), so it’s impossible to distinguish which payment is made for which paywalled piece of content. I guess some kind of a dashboard would be the best way to go, but that will probably take a while to implement and may not be on your roadmap at the moment.