yeah, i'm making an access paywall, as it happens.

adding the ability to hook it into other things than just subscribing to the relay is definitely possible. i'm not sure what it would require exactly, i will have to think about it. i am writing code to handle a subscriber list now, so i guess it's going to be a lot of generic and similar things, just need to plug in some other parts to make it usable for stuff like generating a download link, and this. maybe webhooks would be the way, so the payment triggers a message to another server that then does the download link that expires after some time that directs the user to the intended download.

i can see how this might be done and how it is just a tiny bit different from a relay subscription system.

it might be a while before i get to doing it though. but i'm starting to get contributors and people wanting to use #orly so maybe i can ... well... put an issue up... https://orly.dev - if you know someone familiar with the requirements, make an issue on the repository and maybe someone can implement it.

it does need the pieces i'm in the middle of completing though, monitoring a lightning wallet for payments, parsing the LN payment info in some way (i was going to use zapping a bot npub that is the relay's identity, and who publishes the notes that only the user can read.

so, yeah, still, put an issue, and maybe someone can help if i can't get to it.

it's my main ambition with nostr to actually solve for the business use case and that will make it into a full time job for me, down the track.

Cool, thanks for all you're doing! Well done!

Reply to this note

Please Login to reply.

Discussion

No replies yet.