Grabbed some notes for the next wave of UI cleanup, thanks!
Identities
Plan is to scavenge anything from an identity that might already exist from the network for people that use their social nostr keys, need to think about how to implement edits carefully so folks don't accidentally overwrite their Nostr profiles in that case.
Ideally I'd like to link this out to a social app front-end that's based around web pages for receiving payments
(leveraging offers to the max)
Automation
This is a barebones cron-job like functionality for recurring payments, you can add a rule to pay an offer/lnurl automatically based periodically
Not super-robust yet as it's all wallet side, need to move it to the Pub-side so it doesn't depend on the wallet being open... or we could use the coming push notifications for reminders
Linked Apps ... It’d be cool if we could edit the name of each rule
Noted. The original intent for this was services would use persistent service keys, so the app in your case would have shown "Stacker News" and had an appropriate avatar from the Nostr network
... but SN doesn't actually run a nostr-based service, the SN wallet pairing is client side so each user is doing it with an ephemeral own key.
We should allow for labeling in that case.
Offers
These are analogous to LNURL's or Bolt12 offers, except they use Nostr so they work infinitely better.
The other settings there are event triggers so the offer can accept additional parameters from the payer for products and services etc. When a payment comes in for a given offer the Pub can then callback to an external webhook on payment... that would be something like a fufillment system for orders or custom app that does a thing when someone pays you.
I made a web app for @Car at PlebLab that uses Offers to power it, it's just a static page sitting on GitHub that just takes an offer as an argument for the payment endpoint
Grabbed some notes for the next wave of UI cleanup, thanks!
Plan is to scavenge anything from an identity that might already exist from the network for people that use their social nostr keys, need to think about how to implement edits carefully so folks don't accidentally overwrite their Nostr profiles in that case.
Ideally I'd like to link this out to a social app front-end that's based around web pages for receiving payments
(leveraging offers to the max)
This is a barebones cron-job like functionality for recurring payments, you can add a rule to pay an offer/lnurl automatically based periodically
Not super-robust yet as it's all wallet side, need to move it to the Pub-side so it doesn't depend on the wallet being open... or we could use the coming push notifications for reminders
Noted. The original intent for this was services would use persistent service keys, so the app in your case would have shown "Stacker News" and had an appropriate avatar from the Nostr network
... but SN doesn't actually run a nostr-based service, the SN wallet pairing is client side so each user is doing it with an ephemeral own key.
We should allow for labeling in that case.
These are analogous to LNURL's or Bolt12 offers, except they use Nostr so they work infinitely better.
The other settings there are event triggers so the offer can accept additional parameters from the payer for products and services etc. When a payment comes in for a given offer the Pub can then callback to an external webhook on payment... that would be something like a fufillment system for orders or custom app that does a thing when someone pays you.
I made a web app for @Car at PlebLab that uses Offers to power it, it's just a static page sitting on GitHub that just takes an offer as an argument for the payment endpoint
Very easy to vibe code your own with the CLINK SDK https://www.npmjs.com/package/@shocknet/clink-sdk
I plan to do a vibe coding with CLINK video at some point soon