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.
There are already some explicit relays that exist.
There are also relays over tor. Unsure if mostly alternative access to public relays or different content.
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.
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.
Would you like to test my new service? Let's go!
Now you can put any blog post, painting, picture, or anything else behind a Lightning paywall in seconds.
Withdraw whenever you want, it's transparent with full transaction history. You can even use your own node.
It's not ready but basic functions are working, don't store large funds: https://www.zapit.live/
When I used create login key, I kind of got stuck after it gave me the credentials. It needs a back button or something after you have a key.
Would you like to test my new service? Let's go!
Now you can put any blog post, painting, picture, or anything else behind a Lightning paywall in seconds.
Withdraw whenever you want, it's transparent with full transaction history. You can even use your own node.
It's not ready but basic functions are working, don't store large funds: https://www.zapit.live/
This will be perfect for submitting Highschool assignments. Make the teacher pay 😉
Good to go. My script worked flawlessly. I onboarded 50+ people manually last week… lol. Automation is better.
Remote relay administration too. Admin pubkey can send commands to their relay via events.
Personalised relay feed for pubkey, based on a web portal or similar - like filter events with ‘Facebook’ before sending to me. Or Nthdegree events only.
Access premium features that are too costly to provide to everyone for free - search, POW generation, extra metadata on events, perhaps media caching, etc.
Unlocking higher rate limiting. For example re-broadcasting a backup.
Perhaps access to your recently deleted events.
I’ll keep thinking. It does have a privacy consideration which isn’t ideal - but can’t see how you could get past that.
I’ll setup your access when I have a moment and DM you 🙂
I want to test my automated on-boarding script anyway, haha.
My Nostr POW Service was one of the first to implement it.. and it’s not specifically a relay 🙂
NostrGraph Dashboard now shows you your ZAPs! I’ll try add stuff like most ZAPPed events and whatever in future.
https://nostrgraph.net/dashboard/zaps
#[1] I’m seeing a few bad requests from the Nostrgram client due to the two URLs being merged I think. There is a \n between them, but not a space directly.
NostrGraph Dashboard now shows you your ZAPs! I’ll try add stuff like most ZAPPed events and whatever in future.
https://nostrgraph.net/dashboard/zaps
For clarity too.. I still don’t log all sent zaps due to WOS and other wallets not providing enough details to verify them as valid. Hopefully it’s added and it should work without me changing anything.
NostrGraph Dashboard now shows you your ZAPs! I’ll try add stuff like most ZAPPed events and whatever in future.
https://nostrgraph.net/dashboard/zaps
What is the retail price? How do the economics even work?
I played with JWT today, and it’s not the best fit for use. Hadn’t implemented it before.
I really only wanted a 20,0XX kind defined and basic JSON event. Then browser extensions can tell you that you are signing a “WebApp login” event instead of “Unknown”. I also use an “origin” tag, as opposed to “relay”.
A suggestion to optionally include the users preferred relays in the login JSON event as tags was a good idea for any server side rendering - however not something I need at present. And extension relays and kind 10002 don’t sync, so that’s another issue.
Overly complex scam?
NIP-7 has some discussion two. I don’t need the generic sign function anymore, but we still need a consistent way to support web app login from extensions. An alternative is Nostr Connect - but I think simple extension support is required too. A suggestion was clicking an extension to sign in, but it has limitations too.
My POC works fine and is simple, however perhaps using JWT is a better approach long term and something to spec up. @mazin, you’re still planning relay login to customise pubkey preferences? Happy to collaborate on this too.
https://gist.github.com/blakejakopovic/b0065b9327c48c148bfe989c08137ba1