And not sure if you need/want more validation around the url. I used a number, which was good, but the open url button tries to open a relative link then.
Also, would be cool to add the name and descriptions dynamically into the paywall url - so the link media preview can be more contextual.
Otherwise, nice. Good job. Everything worked well.
I can see my wallet and sats deposited. Now to sit back and wait until my paywall builds my retirement fund.
Thank you so much ššš
Ha. Oh. Maybe make it extremely obvious too they need their wallet address to manage or transfer any earned funds.
Main reason is lots of people are used to zaps (direct into their nip05 wallet) and may not think or know about your lnbits setup. Iād imagine you can always recover their access - but Iām not 100% familiar with your setup.
Yes, I can do that. That's why I asked for a public key, but I should add some more verification parameters.
My ultimate goal is to make the process fully automated, so that funds are not stored on my instance. I am currently able to do this, but it is not yet fully reliable,
Therefore, I will add this fully automated feature only when it is very reliable which Split Payment option.
Dashboard will have its own wallet button, so you just click it and enter your wallet. I will take a session time approach for that,
including a scrub feature so funds can directly transfer to your own personal wallet. There is some problem with the invoice listener, but I am resolving that.
Once that's resolved, we can eliminate the requirement of a secondary wallet.
