I like this nip PR: https://github.com/nostr-protocol/nips/pull/901
Maybe that's not quite what you're asking.. but I think there could be some value in this method, since it is very useful for people paying direct from an app with nwc for example..
How do pay 2 poast relays ask for payment when receiving an event? Invoice on the OK response? cc nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hsvlnggv
Discussion
These NIPs all try to solve problems caused by:
1️⃣ Daily drivers currently being Twitter clones, instead of Chat apps
2️⃣ Hosting solutions not having an identifier with agency (key pair)
3️⃣ DMs not being fleshed out enough yet
DMs van work fine for subscriptions etc...
For #Pay2Publish communities we need something else tho. And it can maybe just be a zap to the #communikey. A (cashu /ln) zap that references the event to be published of course.
Or was that not one of the reasons for your question nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg ?
Yeah that's what I was thinking: you send the event, get back OK response with payment-required message with amount, send (nut)zap tagging the original event and both events are now accepted. Makes sense?
For those looking to reach me personally for all things related Bitcoin or Nostr , you can connect with me on (simpleX chat app) using my invitation link below 👇👉
Just keep in mind that you cant just send an invoice. You have to tell people what they are paying for... A sub? A one-off thing? And for which account. Clients can't know all of that. You will need to write a full message explaining it.
I love seeing this in action with the wine relays. It works really well. One less thing to remember & one less dm to check.